feat: additional features extending defaults in multi-site #1191
Conversation
This file contains 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
dhhyi
added
enhancement
MaxKless
force-pushed
the
feat/additional-features-multi-site
branch
from
e9d3e47
to
6cbe371
Compare
MaxKless
approved these changes
Jul 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Type
[x] Feature
What Is the Current Behavior?
Using multi-site deployments, if you have a default feature list in the brand-specific environment.ts file, and on certain channels - but not all - you want to go live with another feature, it is currently required to repeat the whole feature list for all of those channels.
What Is the New Behavior?
New property
addFeaturesin multi-site config, that allows adding additional features that extend the feature list for the specific channel.Does this PR Introduce a Breaking Change?
[ ] Yes
[x] No
Other Information
AB#77608