Fix: In blueprint vars handle the case sensitive case in lookup#4987
Closed
themisvaltinos wants to merge 1 commit intomainfrom
Closed
Fix: In blueprint vars handle the case sensitive case in lookup#4987themisvaltinos wants to merge 1 commit intomainfrom
themisvaltinos wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Blueprint variables with mixed case (e.g., Customer_Name) were not recognized when referenced in certain places we look up with lower name (as the rest of the variables). This caused a mismatch between the stored variable names (which are stored not lower case) and the lookup logic. This fix updates the blueprint variable lookup to check exact case first then fall back to lowercase instead of storing as lowercase as the less intrusive fix, but let me know @georgesittas what you think