-
Notifications
You must be signed in to change notification settings - Fork 229
Added support for @generated marker #382
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
Signed-off-by: Antonín Říha <[email protected]>
I think sticking to the same format as protoc might be a good idea, the |
Signed-off-by: Antonín Říha <[email protected]>
Yes you are probably right, it seems that it just has to be somewhere at the beginning (not clearly defined). But from examples I found it seems that it can be below. |
One more idea would be to regenerate the pre-compiled files in lib/google/protobuf |
Signed-off-by: Antonín Říha <[email protected]>
I regenerated all the lib/google/protobuf files. Looking at the output it seems like the generated files had wrong documentation for attributes (before attribute definition, not after). So this also fixes that. |
Thanks, this looks great |
This PR adds support for @generated marker as specified at https://generated.at/ This marks generated code as such and allows it to be skipped in CI/CD. I am just not sure if this is the right format or if adding it after current message would be better.