Skip to content
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: continue get_classnames loop after adding the default classname #60153

Merged
merged 1 commit into from Mar 25, 2024

Conversation

ramonjd
Copy link
Member

@ramonjd ramonjd commented Mar 25, 2024

What?

Quick janitorial PR that continues the get_classnames loop after adding the default classname.

Why?

Because we've added the classname by virtue of testing for true, and besides, get_slug_from_preset_value only works on a string, not a boolean.

How?

continue;

Testing

There are no material changes.

CI should pass.

…classname, and besides, get_slug_from_preset_value only works on a string.
@ramonjd ramonjd added [Type] Code Quality Issues or PRs that relate to code quality [Package] Style Engine /packages/style-engine labels Mar 25, 2024
@ramonjd ramonjd self-assigned this Mar 25, 2024
@ramonjd ramonjd changed the title Style Engine: continue get_classnames loop after adding the default classname Mar 25, 2024
Copy link
Contributor

@andrewserong andrewserong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! LGTM and quickly smoke tested the editor 👍

Copy link

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: andrewserong <andrewserong@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@ramonjd ramonjd merged commit bae7201 into trunk Mar 25, 2024
62 checks passed
@ramonjd ramonjd deleted the update/style-engine-get-classnames-continue-on-true branch March 25, 2024 07:08
@github-actions github-actions bot added this to the Gutenberg 18.1 milestone Mar 25, 2024
carstingaxion pushed a commit to carstingaxion/gutenberg that referenced this pull request Mar 27, 2024
…classname, and besides, get_slug_from_preset_value only works on a string. (WordPress#60153)

Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
cbravobernal pushed a commit to garridinsi/gutenberg that referenced this pull request Apr 9, 2024
…classname, and besides, get_slug_from_preset_value only works on a string. (WordPress#60153)

Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Package] Style Engine /packages/style-engine [Type] Code Quality Issues or PRs that relate to code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants