-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Style engine: update terminology and docs #41964
Conversation
Gathering a list of terms.
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.
Nice one, thanks for improving the documentation and adding better clarity to the variable names 👍
It's a bit nit-picky, but I left a couple of comments to see if we need the _array
suffix on the variable names. I was wondering if we changed some of the names to be more different to each other, if that'd remove the need for the suffix?
Whoops I broke something 😸 Unit tests failing... Fixing... |
Cleaning up a few loose ends. Definition should have been declaration :D
Fixed! T'was a typo. |
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.
Thanks for the updates @ramonjd, the changes look good to me, and I smoke tested to make sure it's still working with server-generated styles and individual sides:
LGTM 🎉
What?
This PR adds a glossary that contains terms and definitions used by the style engine.
It also updates comments and var names so that they're consistent with the definitions.
Part of:
Why?
To ensure consistency and to reflect proper usage.
How?
⌨️
Testing Instructions
Direct link to README.md (so you don't have to parse through HTML tags)
npm run test-unit-php /var/www/html/wp-content/plugins/gutenberg/packages/style-engine/phpunit/class-wp-style-engine-test.php