Add cleaning of substrings of require
messages from parsed construc…
#4764
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.
…tor arguments
Close #4758
Motivation
In some cases in parsed constructor arguments appear some strings which are substring of messages used in required statements in constructor. As in linked issue:
Parsed constructor arguments:
596f75206e65656420746f2070726f7669646520616e2061637475616c204372{constructor_args_itself}
Require messages:
596f75206e65656420746f2070726f7669646520616e2061637475616c2043727970746f7374616d7020332e3120636f6e74726163742e
=>You need to provide an actual Cryptostamp 3.1 contract.
596f75206e65656420746f2070726f7669646520616e2061637475616c2043727970746f7374616d7020332e312050726573616c6520636f6e74726163742e
=>You need to provide an actual Cryptostamp 3.1 Presale contract.
Changelog
Bug Fixes
Checklist for your Pull Request (PR)
CHANGELOG.md
with this PRmaster
in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.