-
Notifications
You must be signed in to change notification settings - Fork 81
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
smartcontract: fix DO NOT EDIT warning to autogenerated files #3280
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3280 +/- ##
==========================================
- Coverage 85.30% 85.21% -0.10%
==========================================
Files 327 327
Lines 44153 44248 +95
==========================================
+ Hits 37664 37705 +41
- Misses 5001 5047 +46
- Partials 1488 1496 +8 ☔ View full report in Codecov by Sentry. |
@@ -60,7 +60,9 @@ const ( | |||
// verification contract is circuit-specific, i.e. corresponds to a specific | |||
// single constraint system. Thus, every new circuit requires vew verification | |||
// contract to be generated and deployed to the chain. | |||
goVerificationTmpl = `// Package main contains verification smart contract that uses Neo BLS12-381 | |||
goVerificationTmpl = `//Code generated by neo-go zkpbinding.GenerateVerifier; DO NOT EDIT. | |||
// |
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.
but not be attached to the package clause
So it has to be a separate comment, right?
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.
Does it mean it needs space between two comments?
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 so. Try finding some similar tools and check how exactly it's structured there.
Like
// Code generated by "stringer -type=Role"; DO NOT EDIT.
But this doesn't have package-level documentation, unfortunately. My primary concern is correct package doc. You can check it with godoc
though.
The text must appear as the first line of a properly formatted Go // comment, and that comment must appear before but not be attached to the package clause and before any /* */ comment. Closes #3254 Signed-off-by: Ekaterina Pavlova <[email protected]>
bcacde2
to
1237c71
Compare
Change the order of comments
Closes #3254