fix: handle non-standard field casing in MapContains queries #666
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.
Modified processMapContainsQuery to support Map fields with uppercase/non-standard casing (e.g., 'Positions' instead of 'positions'). The method now tries both the standard lowercase naming convention and the original field name when resolving Map fields.
This fixes repository methods like findByPositionsMapContainsCusip when the Java field uses non-standard casing to match JSON data from external sources like RIOT exports.