Preserve enabled key for collection variables in v1 normalizer iff it is present and is false#496
Open
Harsh-Bansal wants to merge 1 commit intodevelopfrom
Open
Conversation
…normalizer iff it is present and is false
Author
|
@coditva @codenirvana will be adding the test cases post discussion of approach and the issues it is fixing. |
codenirvana
force-pushed
the
develop
branch
from
ba2d3e5 to
e4b3da0
Compare
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
2 participants
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.
Preserve
enabledkey for collection variables in v1 normalizer iff it is present and is false.This is being done to fix enabled/disabled info getting lost in normalize operation.
Note: As with disabled, we preserve the enabled field only when it indicates variable is not active.