-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
ZMS-154 #693
Conversation
🎉 It's complete now? If you'd like I can review it in a little bit |
Yes, @NickOvt has been busy with it, and finally, no more yaml wrangling by hand 🥳 All the endpoints are documented as well, even the most obscure ones. |
@louis-lau If you have time then of course you can review it! |
On first look the spec doesn't seem to be a valid openapi spec, lots and lots of errors. I'll take a look. |
I've opened PR #694 and PR zone-eu/restify-api-generate#15 These should at least fix the spec so it's an openapi spec and there are no errors. There's still various warnings though. Can I leave fixing those to you @NickOvt? You should check the spec on https://editor.swagger.io/, you'll see the warnings in the sidebar. For example, this isn't really valid: password:
type: string
description: New password for the account. Set to boolean false to disable password usage for the master scope, Application Specific Passwords would still be allowed
enum:
- false
- ''
Even if the type did match, the enum suggests the value here can only be I also think we should set the operationIds manually per endpoint instead of having restify generate them automatically. We should be able to just use the old ones. For HTML docs it doesn't really matter much, but when generating api clients it matters quite a lot. It essentially determines the function name you'll be calling. For example, with the old spec I'd be calling: this.messagesApi.updateMessage() In the new spec that would be: this.messagesApi.putusersusermailboxesmailboxmessages() I'm sure you agree that that's not very readable haha I haven't looked at the content of the schemas etc yet, will do that later. Very excited to have this automatic generation! |
Change old documentation file for the new autogenerated one