-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
detail which parts of the API are implemented #7
Comments
nope I have not done this, but it would definitely be a good idea. I'll get on it this weekend or so 👍 |
Coupled with #18, client apps will be able to provide UI tailored to the exact capabilities of each version. |
I wrote a script to rudimentarily check for implementation details. It works by reading what is posted on the Subsonic API page then searching
|
@thecarlhall thank you very much for that. very handy |
Here are the scripts I used to generate this: https://gist.github.com/thecarlhall/718de74c702e5d7993260e42d7160507 |
Seconding this. I am looking for a subsonic implementation that supports bookmarks for audiobooks, so it would be great to know which subsonic API version this supports. |
thanks to @brian-doherty we have many more endpoints implemented so I'll add a wiki page describing them before the next release |
the "Subsonic API" actually varies with time (different releases) and space (different forks) so it would be quite interesting to see which parts are actually implemented in gonic. the supysonic server has this API implementation status page which details what they implemented and why. for example, shares are not implemented and might never be. it also has a list of revisions to the API which could prove quite useful.
has equivalent work been done on gonic?
thanks for this nice project!
The text was updated successfully, but these errors were encountered: