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
Instead of ignoreTag it could be named ignoreTags and allow to contain CSS selectors like other posthtml plugins as posthtml-match-helper accepts [tag]#[id].[class]. E.g div#id. It would not require the developers to insert extra wrapper tags and modify the html at all. E.g. with
constoptions={ignoredTags: ['div#id','.ignore']}
would not alter
<divid='id' data-attrib='{{attribute}}'>and {{content}} not meant to be altered</div>
or
<divclass='.ignore' data-attrib='{{attribute}}'>and {{content}} not meant to be altered</div>
at all.
Further more similarly other ...Tags options could use the same logic similarly to Angular Structural directive like
<div*ngIf="[condition]"></div>
The text was updated successfully, but these errors were encountered:
I like the idea, though changing its name would mean a breaking change. Maybe we could do ignoredSelectors or something until the next major release, what do you think @Scrum?
I think the logical approach is ignoredSelectors. We can also make an interim release in which we explicitly indicate the deprecation of the parameter ignoreTag and an exception in future releases.
You must also specify that ignoredSelectors will include the parameter value ignoreTag.
Instead of
ignoreTag
it could be namedignoreTags
and allow to contain CSS selectors like other posthtml plugins as posthtml-match-helper accepts [tag]#[id].[class]. E.gdiv#id
. It would not require the developers to insert extra wrapper tags and modify the html at all. E.g. withwould not alter
or
at all.
Further more similarly other
...Tags
options could use the same logic similarly to Angular Structural directive likeThe text was updated successfully, but these errors were encountered: