fix: Add --preferPlainHtml flag#2724
Conversation
| // Try .plain.html | ||
| const plainHtmlFile = path.resolve( | ||
| // Try second extension | ||
| const secondFile = path.resolve( |
There was a problem hiding this comment.
rather than first/second have you considered an approach where an arbitrary length array of options is allowed? (if it helps simplify, otherwise probably not worth it)
|
@davidnuescheler @kptdobe why is there a fallback to |
|
Because you approved it - see #2631 |
|
In experience modernization agent we're generating .plain.html that are both used to show the user a "preview" of their content and then get uploaded to DA once the user is satisfied. Considering the new "aem content" approach it might make sense to look at going "back" to generating .md files, but for now we're still using ".plain.html", so it makes sense to have a way to have a way to "prioritize them". |
@karlpauls I'm not sure anymore why we need to serve the |
4 participants
Add an opt-in --prefer-plain-html flag to aem up so .plain.html wins over .html sibling in --html-folder mode
Related Issues
https://github.com/Adobe-AEM-Foundation/aem-experience-catalyst/issues/1129