This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
Fix bug where Camel/Pascal cased variables were broken in filters #325
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
Codecov Report
@@ Coverage Diff @@
## master #325 +/- ##
======================================
Coverage 95.4% 95.4%
======================================
Files 10 10
Lines 2350 2350
======================================
Hits 2242 2242
Misses 108 108
Continue to review full report at Codecov.
|
|
Perfect - thanks @whostolebenfrog! |
This was referenced Jan 8, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This fixes a bug where if types had a cased name e.g.
MovieWithCasethen it would be incorrectly referred to later in the query resulting in both an unbounded match and incorrect results.I believe this should resolve these two open issues:
#309
#257