You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generated classes like CheckedFunction0 could be annotated with javax.annotation.Generated to differentiate them from hand written code.
Furthermore the generator class as well as the actual generator method could be referenced via the comment attribute to ease finding the appropriate generator method.
The text was updated successfully, but these errors were encountered:
thank you for your suggestion! Could you please elaborate on the use-case(s)?
Currently we ensure that PRs will fail when generated code is manually modified. Our CI build does this by...
performing a git clone (which may contain manually modified generated code)
running the build (which overwrites generated code)
checking for changes using git status (there shouldn't be changes)
By using annotations, we make the 'is generated' property part of the public API. Our users should not bother whether source is generated or not. We need the freedom to change that property without affecting backward-compatibility.
Generated classes like CheckedFunction0 could be annotated with
javax.annotation.Generated
to differentiate them from hand written code.Furthermore the generator class as well as the actual generator method could be referenced via the comment attribute to ease finding the appropriate generator method.
The text was updated successfully, but these errors were encountered: