feat(api-server): remote control api #1909
No reviewers
Labels
No labels
awaiting-reply
breaking changes
bug
cannot-reproduce
dependencies
documentation
duplicate
electron-issue
enhancement
fix-available
good first issue
help wanted
invalid
javascript
need more information
need rebase
official-youtube-music-issue
plugin request
question
release
security
stale
Status: blocked
typo
wontfix
ytmd-issue
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: YTMD/youtube-music#1909
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/api-server"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Notes
Please add versioning 🙏
Huh, I resolved the conflict and Snyk is now mad at me :(
I assume a new vulnerability was found between the previous merge and my merge?
What's blocking this from being merged currently? I'd love to adapt my integrations based on this PR
I'll give this a thorough look tomorrow.
As for why it is not merged, I think it is still in progress.
I squashed the commits and resolved the conflict, you can find it here.
(Note that I won't be opening a PR to merge that branch into this one, it is just for testing)
--
I ran into an issue, I couldn't authenticate using the bearer token given to me by the api.
Steps taken:
/auth/{id}
(id
=a
) and receive a json response that contains the JWT/auth/{id}
and provide the JWT in the formAuthorization: Bearer {JWT}
Unauthorized
responsePS: I had the auth strategy to none.
PS2: I have a huge headache, so I didn't end up giving this a thorough look :(
TODO: processing CORS with
hono/cors
Hey, who is responsible for this PR? I'd love to move this along for all the cool integrations to be possible. If there are still changes needed I'm willing to work on them. Please let me know if I should take over this feature @JellyBrick. Kinda painful to see it stuck in limbo for this long 🫠
@JustMrPhoenix merged
i am having issue using the api key.
i am on /swagger page and got a access token. upon adding that token to authorize on top of page I should be able to tryout routes.
but it keeps on saying unauthorized
this is the curl request it generates. what is wrong here ?
I had to disable and enable the plugin for it to start working, maybe that'll also fix it for you