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.
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
Introduce
prepend_to_selector()
to avoid additional if checks and follow single responsibility principle #50266Introduce
prepend_to_selector()
to avoid additional if checks and follow single responsibility principle #50266Changes from 2 commits
7e8cc35
45473d9
b9c0312
32332f8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
As noted in a Slack DM to @felixarntz:
A
$to_prepend
of".some-class "
will produce:.some-class h1,.some-class h2,.some-class h3
.This was the result prior to this PR though. See this 3v4l.
One way to achieve the result in the docblock is
trim( $sel )
andimplode( ', ', $new_selectors )
. See this 3v4l.I'm not sure if these "misplaced" spaces were already known and accepted, or if this is something tests should have caught.
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 @costdev, good catch!
We could add
trim()
to the function, but to me that seems like a separate conversation. The output withtrim
would be preferable, but it's also not a big deal to have the extra space, and since the function is called tons of times there may be some (probably insignificant) performance cost to it.In other words, I'm by no means opposed, but potentially this could be discussed in a separate issue / PR.
I have fixed the doc block to include the double spaces to clarify that.
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.
Sounds like a plan @felixarntz!
For a separate issue / PR, as an alternative to the
trim()
, if we know that the format always includes a space after the comma, we couldexplode( ', ', $selector )
andimplode( ', ', $selector )
. See this 3v4l.