Do not show Configuration diff for PreDeployments #879
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.
This PR avoids showing the Configuration diff view for each attribute in the configuration when looking at a
PreDeployment
Intent
Type of Change
Approach
The approach here was to avoid passing
deployment
down to every Configuration component and checking if it was a pre-deployment. Instead we can check that directly in theConfigSetting.vue
component which determines whether or not to show the plaintext value or the diff views. To do this without a lot of nested props we can use Provide / Inject.Since all attributes are new (since this PreDeployment has never been deployed) we need to check if this is a
PreDeployment
so new attributes still work for Redeployments.