Extract element ingredient migrator #2337
Merged
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
Then we are able to call this from a data migration or rake task from apps.
It might be the case that ingredients are defined on an element that does not have a equivalent content. We want to make sure that the element is exaclty is how it is defined in the elements.yml after the migration. If the content could not be found, we just skip copying the data.
mamhoff
approved these changes
May 11, 2022
tvdeyen
added a commit
that referenced
this pull request
May 11, 2022
…ator Extract element ingredient migrator
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.
What is this pull request for?
Then we are able to call this from a data migration or rake task from apps.
Also ensure all ingredients get created during migration.
It might be the case that ingredients are defined on an element
that does not have a equivalent content.
We want to make sure that the element is exaclty is how it is defined in the elements.yml after the migration.
If the content could not be found, we just skip copying the data.
Checklist