Pass the Gallery v2 Flag over from the editor#16832
Conversation
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
|
You can trigger an installable build for these changes by visiting CircleCI here. |
5a8f8ce to
df7f892
Compare
|
|
||
| // Experimental Features | ||
| let galleryKey = BlockEditorExperimentalFeatureKeys.galleryRefactor.rawValue | ||
| let galleryRefactor = BlockEditorSettingElement(name: galleryKey, |
There was a problem hiding this comment.
Since this flag is expected to be temporary I'm storing it in the BlockEditorSettingElement as a new type experimentalFeatures
|
Hey @chipsnyder 👋 |
That sounds like a good plan to me 👍 Thank you for keeping an eye on that parent issue |
@chipsnyder Indeed this parameter was renamed from |
antonis
left a comment
There was a problem hiding this comment.
Great work @chipsnyder 👍
This LGTM 🎉
* Add Gallery flag to editor session start * Update analytic key names for gallery refactor
…-blocks-editor-settings_v2 # Conflicts: # Podfile # Podfile.lock
mkevins
left a comment
There was a problem hiding this comment.
I tested these changes and everything is working as expected. Thanks for adding this!
Just needs conflicts to be resolved before merging. 👍
…-blocks-editor-settings_v2 # Conflicts: # Podfile # Podfile.lock
Related PRs
gutenberg:WordPress/gutenberg#33314gutenberg-mobile:wordpress-mobile/gutenberg-mobile#3713WordPressKit-iOS:wordpress-mobile/WordPressKit-iOS#417Description:
This PR is built off of #16823 That PR should be reviewed and merged before this one.
To test:
This can be tested with the instructions contained here: WordPress/gutenberg#33314
Regression Notes
Potential unintended areas of impact
This could also affect the changes for Global Style Settings
What I did to test those areas of impact (or what existing automated tests I relied on)
They can be retested with:
These changes are covered by the existing Unit Tests
PR submission checklist:
RELEASE-NOTES.txtif necessary.