-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix case sensitivity #285
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
Fix case sensitivity #285
Changes from all commits
Commits
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.
Do the toLower calls on lines 521 and 527 need conditionalizing as well?
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.
And if so, is there a test case that could exercise that path?
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 don't think so. In fact, I don't think we even need to check for the nil condition there.
go/reflect_struct_decoder.go
Lines 516 to 519 in 7cceb6c
Here
decoder
is ageneralStructDecoder
, which is created here:go/reflect_struct_decoder.go
Line 485 in 7cceb6c
The
fields
in this struct comes from:go/reflect_struct_decoder.go
Lines 31 to 34 in 7cceb6c
The
*structFieldDecoder
is a*StructDescriptor
which is created from:go/reflect_struct_decoder.go
Line 14 in 7cceb6c
go/reflect_extension.go
Line 324 in 7cceb6c
which creates from:
go/reflect_extension.go
Lines 388 to 391 in 7cceb6c
From the above snippet ^,
*StructDescriptor
can never be nil.Also, if the decoder is supposed to be case sensitive, the conversion to lower case is taken care of while constructing the struct decoder:
go/reflect_struct_decoder.go
Lines 35 to 39 in 7cceb6c
so the
toLower()
which is used below in lines 521 and 527 is not called and not needed.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.
If this makes sense, I'll remove the lines. But I want to first double check if this is indeed correct.
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.
That's my understanding as well. I agree that we should remove the lines.
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.
Removed.(tests were failing, investigating why)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.
Wait, if the decoder is case insensitive, we need to keep the lines, because
decoder.fields[field]
might return empty, and we can only find the decoder viadecoder.fields[strings.ToLower(field)]
.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.
Yup, added back the lines along with a new test case.
@liggitt the case insensitive ones are the ones that exercise the path.
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.
+1