feat: use new Forma 36 Layout component [UFO-1876] #9971
Merged
Conversation
This file contains hidden or 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
✅ Deploy Preview for ecommerce-app-base-components canceled.
|
veu
changed the title
Lelith
approved these changes
Jul 9, 2025
cf-remylenoir
approved these changes
Jul 9, 2025
mgoudy91
approved these changes
Jul 9, 2025
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.
Purpose
We’re replacing the old Workbench component with the new Layout to prepare for the next Forma 36 release. For the Wistia and Salesforce apps this affects the config screens only while for GraphQL Playground it changes the main screen a bit but only for the better.
Wistia config screen before / after
Salesforce config screen before / after
GraphQL Playground main view before / after
Look at all that space!
Dependencies and/or References
https://contentful.atlassian.net/browse/UFO-1876
Deployment
The Wistia app config screen looks a bit broken because of changes introduced last year that were never deployed. I’m not going to fix them here but this should be looked at before deploying the app again.