Conversation
|
See this PR for further context: ava-labs/subnet-evm#1912 |
|
Would it make sense to add a task that generates these files and another for validating that the files are up-to-date, as per the example of other generated files? It's not clear to me what the value of doing a one-time update would be that is not validated by CI. What am I missing? |
This is actually already checked but admittedly not clear through just the text of this PR. The
The only difference is that |
|
I will add explicit deletion to catch orphans. |
maru-ava
left a comment
There was a problem hiding this comment.
Thank you for the generation cleanup. I guess this begs the question of why all of our go generate tasks aren't deleting before generating?
They absolutely should be -- if they were, this issue would have been caught a long time ago, as these |
|
Issue: #4778 |
Why this should be merged
Currently, the committed ABI files are 2 years old, and there is no clear path of how they were generated. This PR deletes those files, and commits the files generated by
compile.goinstead, establishing a source of truth for the generated.abifiles. Additionally the freshness of these files is added to and checked bycheck-generate-bindingswhich run as part of CI.How this was tested
CI
Need to be documented?
No
Need to update RELEASES.md?
No