Add blanket exclusion for all Concordion HTML template folders (incurring loss of 99% point of using Prettier)
Convert existing HTML templates to their Markdown equivalent. (Some advanced features are only available using @FullOGNL and HTML.)
Create Issue @ Concordion to make their tool case-insensitive.
Add / create parser to undo Prettier's opinion.
edit: (clarification per @eligrey which better exemplifies the issue.)
~~The official stance is that DOCTYPE in this context should be case-insensitive.
However, each tool explicitly utilizes a different option.~~
The official HTML standard specifies that DOCTYPE is case-insensitive
Prettier, as an opinionated formatter changed behavior to force lower-case (which is valid in HTML context)
(X)HTML specifications however, need to additionally comply to XML DOCTYPE standards where DOCTYPE is a case-sensitive ID.
Current work-around:
Trunk check / fmt should only affect new and modified code, so once it's manually committed, it shouldn't break.
Forgetting to manually implement the work-around simply results in wasted cycles and an assumption the less-than-obvious stack-trace will trigger recollection of the needed fix.
Example failing build Circle CI build Formatting via Trunk delegates HTML linting / Formatting to Prettier. Prettier then automatically lowercases the DOCTYPE declaration in HTML templates used by Concordion. Concordion then fails with an initialization error when executing the template. (error similar to https://github.com/concordion/concordion/issues/15) Prettier issues: #https://github.com/prettier/prettier/pull/7391 and https://github.com/prettier/prettier/issues/6502 as it expects an Uppercase DOCTYPE.
Fixes:
edit: (clarification per @eligrey which better exemplifies the issue.) ~~The official stance is that DOCTYPE in this context should be case-insensitive. However, each tool explicitly utilizes a different option.~~
The official HTML standard specifies that DOCTYPE is case-insensitive Prettier, as an opinionated formatter changed behavior to force lower-case (which is valid in HTML context) (X)HTML specifications however, need to additionally comply to XML DOCTYPE standards where DOCTYPE is a case-sensitive ID.
Current work-around: Trunk check / fmt should only affect new and modified code, so once it's manually committed, it shouldn't break.
Forgetting to manually implement the work-around simply results in wasted cycles and an assumption the less-than-obvious stack-trace will trigger recollection of the needed fix.