We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add a new type=content to the Markup Mapping config that enables using the TypeMatcher in helix-pipeline.
type=content
TypeMatcher
helix-pipeline
Instead of using a CSS path expression in match, you would then use a content expression like:
match
^heading
heading
paragraph$
paragraph
heading image+
image
heading? image
heading paragraph* image
(paragraph|list)
list
^heading (image paragraph)+$
The text was updated successfully, but these errors were encountered:
docs(markup): describe new content intelligence matching expressions
7a3ced5
see #278
docs(markup): more detailed description of match types
d6c2134
see #278 and #279
16a0916
chore(release): 7.1.0 [skip ci]
1fe3d8d
# [7.1.0](v7.0.1...v7.1.0) (2020-04-22) ### Bug Fixes * **deps:** npm audit fix ([f6c28f5](f6c28f5)) * **markup:** relax markup mapping schema ([fd62ae0](fd62ae0)) ### Features * **markup:** add support for content intelligence matching expressions ([16a0916](16a0916)), closes [#278](#278) * **markup:** add URL matching type ([1902279](1902279)), closes [#279](#279)
🎉 This issue has been resolved in version 7.1.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
trieloff
No branches or pull requests
Add a new
type=content
to the Markup Mapping config that enables using theTypeMatcher
inhelix-pipeline
.Instead of using a CSS path expression in
match
, you would then use a content expression like:^heading
– the first element is aheading
.paragraph$
– the last element is aparagraph
.heading image+
– aheading
followed by one or moreimage
s.heading? image
– an optionalheading
followed by oneimage
.heading paragraph* image
– aheading
followed by any number ofparagraph
s (also no paragraphs at all), followed by animage
.(paragraph|list)
– aparagraph
or alist
.^heading (image paragraph)+$
– oneheading
, followed by pairs ofimage
andparagraph
, but at least one.The text was updated successfully, but these errors were encountered: