Implementing code-less metadata updater and updating dependencies #15
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.
The new
TemplatedMetadataUpdater
allows to deploy this solution without touching a single line of code in most of the cases (even when shuffling the tokens).Usage
The new
METADATA_TEMPLATE
env variable can be set tonull
(metadata is kept as is) or a JSON object that is used in order to update the metadata for each token.Some placeholder keys are also provided for dynamic replacement:
{TOKEN_ID}
{INT_TOKEN_ID}
: a value matching this string exactly will be replaced with the token ID as an integer value{ASSET_URI}
: please remember that the "image" key is already replaced by default!TemplatedMetadataUpdater
Example:
In a collection where tokens have been shuffled (e.g. token number
1234
becomes5678
), you may have the need to update that ID in some properties such asname
.Original metadata:
Metadata template:
App output: