using .addSidebarWidget to add a new extension creates the sidebar at the end of the list of sidebar
Actual Behavior
using .addSidebarWidget to add a new extension removes all default builtin sidebar
Possible Solution
We are currently using the workaround of re-creating all the built-in sidebar widgets in the migration to not blow away the defaults.
Steps to Reproduce
Create a new migration script creating a new Content Type
use the .addSidebar migration method to add a new custom UI extension
run this migration on Contentful using the CLI
Context
We came across this trying to create migrations for a new Content type and adding a translation extension to the content type. When running the migration using the CLI against Contentful, the end result has our new sidebar widget added to the content type, but all the default widgets were now removed.
Expected Behavior
using .addSidebarWidget to add a new extension creates the sidebar at the end of the list of sidebar
Actual Behavior
using .addSidebarWidget to add a new extension removes all default builtin sidebar
Possible Solution
We are currently using the workaround of re-creating all the built-in sidebar widgets in the migration to not blow away the defaults.
Steps to Reproduce
Context
We came across this trying to create migrations for a new Content type and adding a translation extension to the content type. When running the migration using the CLI against Contentful, the end result has our new sidebar widget added to the content type, but all the default widgets were now removed.
Example migration:
We are currently working around this by re-adding all the default extensions:
Environment