SG-37203 [Mockgun] Ensure string comparison are case insensitive #217
Conversation
This file contains 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
|
It's almost 4+ years. This feels pretty foundational to bringing mockgun functionality closer to "real world" use cases. Any update on getting this merged? |
carlos-villavicencio-adsk
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi!
We recently realized that for text field comparisons, Mockgun was case sensitive where a real Shotgun instance was always case insensitive.
This seemed standard behavior so I updated Mockgun to match.
I've also added appropriate tests and new ones to increase text field comparison test coverage.
Let me know what you think.