-
Notifications
You must be signed in to change notification settings - Fork 656
Replace int.Parse() with int.TryParse() to avoid exceptions caused by overflowing values in tags #2703
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
Closed
james-bjss
wants to merge
7
commits into
GitTools:main
from
james-bjss:feature/ignore_integer_overflow
Closed
Replace int.Parse() with int.TryParse() to avoid exceptions caused by overflowing values in tags #2703
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
329e663
Handle failure to parse integers
james-bjss e8c0bf8
fix formatting
james-bjss 6e4d1b6
use TryParse
james-bjss e7628d9
remove stray whitespace
james-bjss 99ae520
fix formatting
james-bjss 69e2000
rename Parse method to TryParse
james-bjss 2159745
replace Parse with TryParse
james-bjss File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this method does not have the
bool TryParse(string, out T)
signature, I'm not sure it should be namedTryParse
. The method signature indicatesParse
while its behaviour indicatesTryParse
. How much breakage would it cause to change the method signature tobool TryParse(string, out SemanticVersionPreReleaseTag)
?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
Int.TryParse()
line in theSemanticVersionPreReleaseTag
defaults the value to null if it's not parseable.Will let you be the guide here as to whether you would prefer to rename the method it back to Parse OR return false on failure and modify the signature as you have suggested above OR take the same approach as in
SemanticVersion.cs
In terms of breakage the only place it seems to be directly called is within
SemanticVersion.cs
when it constructs and returns a newSemanticVersion
and assigns a pre-release tag.The tests do not seem to directly reference this method directly either.
From there there we can decide if we want to do anything about it eg. returning false from
SemanticVersion.TryParse()
which would result in the calling methodParse()
throwing a new Warning exception.NB. All of the code calls
SemanticVersion.Parse()
nothing seems to call theTryParse()
directly. I could follow the same pattern inSemanticVersionPreReleaseTag
and wrap the method?Calling Code in
TryParse()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer consistent use of
TryParse
returningbool
everywhere, if possible.