Specific methods for patch app configuration file scenarios #5641
+390
−302
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.
WHY are these changes introduced?
The current implementation of
patchAppConfigurationFile
is too broad, and we'll need something more specific if we want to switch out for a format preserving patcher.WHAT is this pull request doing?
This PR introduces three new, more intuitive functions for modifying app configuration:
setAppConfigValue
- Sets a single value in the app configuration using a dotted path notationunsetAppConfigValue
- Removes a value from the app configurationsetManyAppConfigValues
- Sets multiple values at once in the app configurationThe original
patchAppConfigurationFile
function is now marked as internal, and all existing usages have been updated to use the new functions. This provides a more declarative API for modifying configuration values.How to test your changes?
dev
command that updates URLs)Measuring impact
How do we know this change was effective? Please choose one:
Checklist