Skip to content

Replace key/common metadata from the challenger, add a config option for which metadata is updated #23

Description

@shsteimer

This is a very similar issue as #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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions