-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat(specs): add OpenAPI spec for Monitoring API #1683
Conversation
✅ Deploy Preview for api-clients-automation ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
@shortcuts The Monitoring API doesn't have API clients, so I'm not sure how to configure this project to just use this spec for documentation. Can you help me? |
Hey, is it bad if the Monitoring API client is generated ? Or is it something that should not be generated ? |
@kai687 I've added the required stuff to make the CI and local tooling recognize the monitoring spec, it might not be enough to do the generation but as of now it already runs the build and linter steps on the specs, so that's great to progress on writing it! you can do |
Today there's none, but the API is documented and public, so we can generate it |
c67cf54
to
6774bc2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few suggestions and a question
Co-authored-by: gazconroy <gazconroyster@gmail.com>
Co-authored-by: gazconroy <gazconroyster@gmail.com>
Instead of silently returning when a tag name is the same as the client name or alias, throw errors. For example, we have the monitoring API and the monitoring tag within that API. Display names can be equal, but not the tag names themselves.
@kai687 I found the issue for the java generation, this should be good now! |
@kai687 the CI fails because the tests I wrote were before the rename of the methods |
431e871
to
b8c0a51
Compare
b1ee994
to
f8ec513
Compare
142cffe
to
97fdea0
Compare
ok wow I found a looooot of bugs in this PR, so glad you did it and sorry for all the commits :D I'm moving unrelated changes to its own PR, then doing a cleanup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wonderful!! and this PR only solved like 3 bugs, so... thanks a lot for the contribution!
@@ -109,6 +109,19 @@ __metadata: | |||
languageName: unknown | |||
linkType: soft | |||
|
|||
"@algolia/monitoring@workspace:packages/monitoring": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't that file generated ?
🧭 What and Why
Create an OpenAPI specification for the Monitoring API.
The Monitoring API is HTTP only and isn't included in the API clients.
🎟 JIRA Ticket: DOC-1132 https://algolia.atlassian.net/browse/DI-1419