You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So based on experience in last project, I just found that we missing some type of validation which would check if alias for new block can be match in migrated doctypes.
Example of case:
3 archetypes blocks with same alias, lets be it cta
3 doctypes: HomePage, ContentPage, ArticlePage
configuration as followed:
the issue is caused by renaming target alias, but we should have some validation in place to throw information in migration log that we have missing target :)
The text was updated successfully, but these errors were encountered:
So based on experience in last project, I just found that we missing some type of validation which would check if alias for new block can be match in migrated doctypes.
Example of case:
3 archetypes blocks with same alias, lets be it cta
3 doctypes: HomePage, ContentPage, ArticlePage
configuration as followed:
the issue is caused by renaming target alias, but we should have some validation in place to throw information in migration log that we have missing target :)
The text was updated successfully, but these errors were encountered: