-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Template Part placeholder - Add title step to creation flow. #33703
Template Part placeholder - Add title step to creation flow. #33703
Conversation
Size Change: +1.51 kB (0%) Total Size: 1.08 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good!
Few things:
- Template part placeholder changes when I click on the new button.
- "Create" button is enabled when the name field is empty.
Screen.Recording.2021-07-30.at.12.56.16.mov
Right 🤔 . Its moving to the patterns setup component, and since there are no patterns registered here that forwards it to the 'create blank' step of that component which triggers creation but doesn't render anything on the page.... Now after talking it out I realize we can make that step render a placeholder as well. 🤣 That seems like something we should do.
Good catch! thanks for taking a look @david-szabo97 😁 |
Changes looking good! Last piece of the puzzle is the e2e test 😄 |
Success |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢 ✅
Description
Related to discussion on #29950 - Adds a title step to the creation flow from the Template Part placeholder. Here we prompt the user with a modal (similar to the "make template part" flow from the block settings ellipsis menu) to change the name of the title from "Untitled Template Part". If the modal is cancelled, we revert to the placeholder and the template part is not created.
How has this been tested?
With FSE enabled, test the following in both the Site and Post editor:
Screenshots
Types of changes
New feature (non-breaking change which adds functionality)
Checklist:
*.native.js
files for terms that need renaming or removal).