-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Update API Documentation #6696
Comments
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
If they don't match, is there a way that the documentation could be auto-generated from the API code? |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Seats still not in the documentation. |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it. |
with #8058 merged, i'd like to reopen this one. i tried the "suggest edits" button on the api reference page but it didn't work. how/where is the API spec generated, and can it be influenced? if so, how? what's missing for this endpoint to make it into the API reference? |
summoning @snipe since Mr. Stalebot doesn't seem to keep the promise of reopening on reply :-D |
Server (please complete the following information):
Is your feature request related to a problem? Please describe.
I'm writing an (up-to-date) Python module for the Snipe-IT API and have noticed that documentation and implementation don't always match.
Describe the solution you'd like
Updated API Reference
Describe alternatives you've considered
Sifting through the code, i'm not always 100% sure what i'm doing is right.
Additional context
One missing feature i found was the /licenses/:id/seats endpoint. It's not here: https://snipe-it.readme.io/reference#licenses
But it's implemented here: https://github.com/snipe/snipe-it/blob/master/routes/api.php#L413 and it works.
I'm not familiar enough with Laravel nor the Snipe-IT project to confidently identify all API features
The text was updated successfully, but these errors were encountered: