-
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
Add e2e test to ensure block bindings work well with symbols and numbers #62410
Add e2e test to ensure block bindings work well with symbols and numbers #62410
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Will it pass without the fix for #62396? 😄 |
Size Change: 0 B Total Size: 1.75 MB ℹ️ View Unchanged
|
'contenteditable', | ||
'true' | ||
); | ||
await paragraphBlock.fill( '$10.00' ); |
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.
I was wondering how it gets saved, but it looks like autosave triggers when opening a preview 👍🏻
What?
Add an e2e case to cover use cases like this one, where symbols and numbers couldn't be used at the start of a binding value.
Why?
To ensure we don't break things again in the future.
How?
I just added a e2e test for a paragraph connected to a custom field. I thought about replicating the same for pattern overrides, but I felt I was just replicating the test. Happy to add it if considered necessary.
Testing Instructions
Tests should pass once this code in WordPress is updated.