-
Notifications
You must be signed in to change notification settings - Fork 6
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 docs explaining generated code and its API #39
Conversation
Motivation: Users should be able to understand how the generated code is structured and how it may change over time. Modifications: Add two docs: 1. Explain the structure of the generate code and how to navigate it. 2. Explain how the generated code may change and hot to ensure it doesn't cause API breakages. Result: Better 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.
LGTM, just left one question.
ones. Existing API will never be removed and deprecated APIs will continue to | ||
function. |
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.
Maybe this is obvious, but should we clarify that "never" means "unless we tag a new major"?
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.
Good idea, I think that's worth stating.
Motivation:
Users should be able to understand how the generated code is structured and how it may change over time.
Modifications:
Add two docs:
Result:
Better docs