fix: merge existing baseEnvironment data and dataPropertyOrder on import #8584
+12
−1
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.
Fixes #6785
Currently when importing e.g. an OpenAPI YAML, the
baseEnvironment
is not updated correctly. Its data is overwritten (not merged with the existing data, which is very annoying) and thedataPropertyOrder
is not updated correctly therefore leading to the issue described in #6785.This PR:
baseEnvironment.data
withbaseEnvironmentFromResources.data
on importbaseEnvironment.dataPropertyOrder
on import