-
Notifications
You must be signed in to change notification settings - Fork 696
docs: Generate API docs for connect-go API #4408
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
base: main
Are you sure you want to change the base?
Conversation
a0a5d02
to
b4c9dad
Compare
e630e92
to
11e9fec
Compare
This adds the preferred but currently undocumented connect API calls. It uses openapi v3 as intermediate format and then generates the documentation page.
11e9fec
to
97047ba
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.
Generic question: why is a generated file committed to the repo?
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.
In it is a very common pattern in Go, basically when doing dependency management using go mod
, not all repo files are included (tests non go files are removed). So often it is impossible to execute the code generation commands then.
There for it is common to commit the generated files (With all of the problems this causes)
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.
LGTM with some nitpicks, looks great!
Co-authored-by: Marc Sanmiquel <[email protected]>
Still needs a bit more tests and attention and removal of AI slop, but the idea is to include this in the user facing documentation.
The actual docs can be fully seen by running:
And the navigate to: http://localhost:3002/docs/pyroscope/latest/reference-server-api/#connect-api