fix(era-independent): correct max length in readStringOfMaxLength error message #1297
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.
Changelog
Context
This PR fixes a bug in the error message generation for the
readStringOfMaxLengthfunction in the CLI parser. Previously, the error message always displayed "128 characters" as the maximum allowed length, regardless of the actualmaxLenparameter value passed to the function. This caused confusion when the function was called with different maximum length constraints.The fix ensures that the error message accurately reflects the configured maximum length by using the
maxLenparameter value in the error message string construction.How to trust this PR
The change is minimal and focused on a single error message formatting issue. The modification:
"The provided string must have at most 128 characters, but it has "show maxLento display the actual maximum length parameterTo verify this fix:
readStringOfMaxLengthwith a string exceeding the limitChecklist