-
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
chaining toReplaceWith #39335
Comments
A new Issue was created by @vlimant vlimant. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign core |
New categories assigned: core @Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks |
Thanks for the suggestion, the chaining of |
awesome ! |
+core |
This issue is fully signed and ready to be closed. |
I was wondering if there is a major issue with allowing
(Modifier_A | Modifier_B).toReplaceWith(something, something_else).toReplaceWith(something_dfiferent, something_else_different)
instead of
(Modifier_A | Modifier_B).toReplaceWith(something, something_else) (Modifier_A | Modifier_B).toReplaceWith(something_dfiferent, something_else_different)
and for other modifier functions
The text was updated successfully, but these errors were encountered: