-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Bug fix: Key delimiters are now case insensitive #2084
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
base: master
Are you sure you want to change the base?
Conversation
djehuti
left a comment
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.
Thank you!
|
I plan on reviewing this soon. cc @sagikazarmark |
|
Apologies for the delay, I do still mean to review this. For now I'll probably lay down some superficial comments, but I intend to do a proper thorough review next week. |
spacez320
left a comment
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.
Thank you for continued work, this seems close. In addition to the tweaks, I would just add a little note in the readme around the delimeter section telling people delimeters are always lowercased, like keys.
Co-authored-by: Matthew Coleman <matthew.e.coleman@gmail.com>
Co-authored-by: Matthew Coleman <matthew.e.coleman@gmail.com>
Co-authored-by: Matthew Coleman <matthew.e.coleman@gmail.com>
Clarify that the delimiter is case-insensitive for alphabetic characters.
|
/label release-note/bug-fix |
spacez320
left a comment
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.
This looks good to me.
|
@sagikazarmark I believe this is ready for your consideration. |
Simply added the
strings.ToLower(v.keyDelim))as suggested and wrote a small test for it.Fixes #2069