-
Notifications
You must be signed in to change notification settings - Fork 644
[NIT-3992] Add linter for imposible json omitempty #3849
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ 3 Tests Failed:
View the top 3 failed tests by shortest run time
📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
eljobe
approved these changes
Oct 16, 2025
auto-merge was automatically disabled
October 16, 2025 10:05
Pull Request is not mergeable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
json:"...,omitempty"
doesn't work for golang arrays if they don't have zero length - if a field is an array type and not slice then it's always included in the marshaled json string. Same for structs, aliases etc.Why it's bad: it's easy to break backward compatibility or even introduce diversion, e.g. if you add optional field to
params.ChainConfig.ArbitrumChainParams
of typecommon.Address
that happens to be typeAddress [AddressLength]byte
, the genesis block state will diverge - when initializing ArbOS, chain config is marshaled to json and saved to arbos state.Solution
The only existing linter for this was: https://github.com/andydotdev/omitlint. However:
So I simply added a new linter to our in-house set. Fortunately, it seems that our codebase is not affected by an incorrect usage of
omitempty
.