Path to a fragment from a template must currently contain '.html' or '.txt' whereas Thymeleaf documentation doesn't use file extension when referencing to a fragment.
So Ogham should follow the same behavior and resource resolution should use variants too to search for fragments.
Steps to Reproduce
1) Create a test that sends an email using a MultiTemplateContent:
Path to a fragment from a template must currently contain '.html' or '.txt' whereas Thymeleaf documentation doesn't use file extension when referencing to a fragment.
So Ogham should follow the same behavior and resource resolution should use variants too to search for fragments.
Steps to Reproduce 1) Create a test that sends an email using a MultiTemplateContent:
2) Create a fragment
fragment/layout.html
:3) Create a template that includes the fragment (
main.html
):Current behavior:
Inclusion of fragment needs the file extension.
<head th:replace="fragments/layout
.html:: header"></head>
Expected behavior:
Inclusion of fragment should not need the file extension.
<head th:replace="fragments/layout
.html:: header"></head>
However, if file extension is explicitly provided, it should also work