Modular template extension follows the master page extension #2044
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is related to the issue #1818.
This builds the modular template extension from the URI's extension (i.e.
http://examp.le/my-page.amp
orhttp://examp.le/other-page.docx
).It fallbacks to
TEMPLATE_EXT
const if URI extension isnull
or empty.For my project :
I'm creating an AMP version of my website in the same theme.
my custom
system.yaml
So I have two template extensions :
.html.twig
for the regular pages and.amp.twig
for the AMP pages.I'm using the same content for the two versions.
If I create a modular page with the
.amp.twig
, Twig will load modular templates with the extension.html.twig
(which will be wrong formated for AMP framework and not validated).