We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
explicit-types
After applying the rule to synthetix v3 codebase few issues were observed
type(uint).max
int(_price)
typeNameNode.typeName
undefined
fixer.replaceTextRange( typeNameNode.typeName.range, this.isExplicit ? EXPLICIT_TYPES[configFileIndex] : IMPLICIT_TYPES[configFileIndex] )
uint[] memory result;
uint256 memory result;
mapping(address => uint)
uint256
Some of the manual rollbacks can be seen in this commit Synthetixio/synthetix-v3@4295243
The text was updated successfully, but these errors were encountered:
thanks a lot @noisekit for this and sorry for the delay I will take a look at this!
Sorry, something went wrong.
@noisekit made fix here #551
now it seems to be working
Thanks. Will wait for the next release 🙏
No branches or pull requests
After applying the rule to synthetix v3 codebase few issues were observed
type(uint).max
andint(_price)
becausetypeNameNode.typeName
isundefined
in this bit of code:uint[] memory result;
is transformed intouint256 memory result;
mapping(address => uint)
is transformed intouint256
Some of the manual rollbacks can be seen in this commit Synthetixio/synthetix-v3@4295243
The text was updated successfully, but these errors were encountered: