-
Notifications
You must be signed in to change notification settings - Fork 153
Add documentation #35
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
Conversation
| or TypeScript declaration files. | ||
|
|
||
| Possible values: | ||
| - `target=js` - generates a `_pb.js` file for every `.proto` input file. |
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.
Should these be separate plugins?
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.
Will discuss in #52
| - `ts_nocheck=false` - do not print the annotation. | ||
|
|
||
|
|
||
| ### `eslint_disable` |
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.
Do we want to expose this option?
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.
I think we can unexpose, same with the other option. Tracking in #53
| `target=ts`. | ||
|
|
||
|
|
||
| ### `ts_nocheck` |
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.
Could we get away with not exposing this option?
bufdev
left a comment
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.
I think we merge this as-is and iterate from there.
This is the first stab at documentation for the library and code generator. To keep things simple, basically the entire documentation is in the top-level README.md.
The docs are structured a bit similar to the protocol buffer language references (see Java). We go through each protobuf type and show what it's looked like when compiled by us. Then there is a separate section for API docs.
There is also a code example based on the examples in the protobuf repository that can be run without having to install any tooling, so it's easy to get started.