You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a general question as I am sure that there was a good reason to merge these two instead of allowing for the flexibility to only remove class or id attributes.
We have a situation where we cant to inline the CSS classes, but preserve the ID of the tag for use by other JS/JQuery code
So my question is whether it is an acceptable idea to split the current _stripIdAndClassAtrtibutes into 2 new ones:
_stripIdAttribute
_stripClassAttribute
Downside is that it is a breaking change - but that could be mitigated by adding new method signatures that take the new properties over the current single one
Any comments appreciated
Thanks
The text was updated successfully, but these errors were encountered:
This is a general question as I am sure that there was a good reason to merge these two instead of allowing for the flexibility to only remove class or id attributes.
We have a situation where we cant to inline the CSS classes, but preserve the ID of the tag for use by other JS/JQuery code
So my question is whether it is an acceptable idea to split the current _stripIdAndClassAtrtibutes into 2 new ones:
_stripIdAttribute
_stripClassAttribute
Downside is that it is a breaking change - but that could be mitigated by adding new method signatures that take the new properties over the current single one
Any comments appreciated
Thanks
The text was updated successfully, but these errors were encountered: