-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add more details on developer documentation #126674
Add more details on developer documentation #126674
Conversation
a6a3ccf
to
67694f4
Compare
…-01-fix-dev-docs-link
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.
Thanks for the PR! It looks fine to me. I wasn't sure whether we should go to that level of detail here but left a few suggestions. Feel free to accept or ignore them. :)
Co-authored-by: Daniel Mitterdorfer <danielmitterdorfer@users.noreply.github.com>
Co-authored-by: Daniel Mitterdorfer <danielmitterdorfer@users.noreply.github.com>
Co-authored-by: Daniel Mitterdorfer <danielmitterdorfer@users.noreply.github.com>
Co-authored-by: Daniel Mitterdorfer <danielmitterdorfer@users.noreply.github.com>
Co-authored-by: Daniel Mitterdorfer <danielmitterdorfer@users.noreply.github.com>
Co-authored-by: Daniel Mitterdorfer <danielmitterdorfer@users.noreply.github.com>
…on/kibana into 2022-03-01-fix-dev-docs-link
Thanks for your feedback @danielmitterdorfer! I am all for any feedback that improves the readability of the guide, so it is much appreciated. |
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.
Thanks for iterating! LGTM
- Use `@throws` when appropriate. | ||
- Use `@beta` or `@deprecated` when appropriate. | ||
- Use `@removeBy {version}` on `@deprecated` APIs. The version should be the last version the API will work in. For example, `@removeBy 7.15` means the API will be removed in 7.16. This lets us avoid mid-release cycle coordination. The API can be removed as soon as the 7.15 branch is cut. | ||
- Use `@internal` to indicate this API item is intended for internal use only, which will also remove it from the docs. |
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.
We use @public
in several places, it's not clear to me what the distinction is, perhaps we should mention that here too?
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.
We don't officially recommend using @public
, it's a convention that I think only the core team uses. I think it'd be great to use, but only if we had ci checks to ensure all public APIs were labeled appropriate, and fail if not. Otherwise it can't be trusted to be accurate.
Co-authored-by: Joe Portner <5295965+jportner@users.noreply.github.com>
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
Friendly reminder: Looks like this PR hasn’t been backported yet. |
best practices
page.Key concepts
andTutorials
.