adobe / adobe/aem-experimentation
Replace key/common metadata from the challenger, add a config option for which metadata is updated
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
This is a very similar issue as https://github.com/adobe/aem-experimentation/issues/15 but running into an issue with a customer trying to use this where the `Template` metadata is used to load dynamic js and their challengers are using different template values.
I think we could safely:
* add a config which is an array of metadata fields to update
* default that value to be `['template', 'theme']`
* update/overwrite those metadata fields when overwriting `main`
Contributor guide
Research direction
Start by tracing the code path that overwrites main with a challenger and review the related issue #15 for context. The change is done when an array configuration controls which metadata fields are replaced, defaults to template and theme, and those fields are updated when main is overwritten.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100