-
-
Notifications
You must be signed in to change notification settings - Fork 724
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experimental feature flag for new add block button enabled by default. #4947
Conversation
✅ Deploy Preview for volto canceled.
|
4 failed tests on run #7051 ↗︎
Details:
blocks/block-anchors.js • 1 failed test • Core Blocks 18.x
volto-slate/03-block-slate.js • 1 failed test • Core Volto Slate 18.x
volto-slate/03-block-slate.js • 1 failed test • Core Volto Slate 16.x
blocks/block-anchors.js • 1 failed test • Core Blocks 16.x
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
We are using some addons that allows adding blocks inside other blocks, like columns, tabs and accordion. There are some issues with these blocks when the experimental feature is enabled. Is the "block inside block" feature native or created by the addons team? Is there something like this native to Volto? If no, are there plans for it? |
@rotavio there is no such add-ons team, only their authors. These change the behavior of the add button in the main stream of blocks. The management of the "blocks in block" use case is done internally by the add-ons (using their own handlers). Recently we included in latest 17a16 the primitive container and the grid block in core. However, these are also detached from the mentioned feature, having their own means and UX to add blocks inside. I am personally not aware that there are issues with other addons (there are none in the core grid). /cc @avoinea @tiberiuichim ? |
Thank you for the information. I understand. |
@rotavio It would be great if you could provide exact instructions for reproducing the annoyance, and screenshots/video. Which add-on are you working with? etc. Thanks! |
@plone/volto-team I had further discussions regarding this matter with a couple Team members who brought up good points: 1.- We really haven't yet a proper alpha testing for including the feature by default This is utterly true, and I didn't realise this has to be the case always. So doing it now at the end of the alpha phase of 17 is useless. 2.- The feedback is still quite few, and a proper alpha phase would have helped. Mostly because of 1. 3.- We still are unsure of the final shape that the Experimental / Future / Feature flags should have, we decided not to change the current shape So I propose to slate this until 18, the first alpha would have it enabled by default (in the shape of the current experimental flag, but turned on). During beta/RC/final release, and if we decide to have it as a default feature, then it should abandon the form of the "experimental" flag and be just another "settings" key (turnable off). |
How we did we would do this?
true