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
Would normalize the excerpt file property to always be { html: '...', text: '...' }
excerpt
{ html: '...', text: '...' }
Pro's:
multipleFormats
stripped
<p>
Cons:
{{ excerpt }}
The text was updated successfully, but these errors were encountered:
Actually this is mostly backwards-compatible, if the object is a new String or has a toString method that returns the html snippet
new String
toString
html
Sorry, something went wrong.
No branches or pull requests
Would normalize the
excerpt
file property to always be{ html: '...', text: '...' }
Pro's:
multipleFormats
option (=simpler API)stripped
, removing only the outer<p>
tagsCons:
not backwards-compatiblecan't just put{{ excerpt }}
in a templateThe text was updated successfully, but these errors were encountered: