fix: disable_cypher_qc and other 3+ segment JSON keys #190
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.
Description
Fixes a bug that caused config keys with more than one underscore to not be parsed.
Regression tests have been added to avoid further issues
Motivation and Context
The previous env var fixes introduced a bug when attempting to find the end of a key when the key contains multiple underscores
How Has This Been Tested?
Additional tests have been added and various configurations with varying numbers of underscores and path segments were reviewed to ensure we have coverage for variations of path sizes and variations of multiple underscores per key.
Types of changes
Checklist: