Skip to content
New issue

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

Qute includes resolution is not intuitive and can be confusing #43907

Open
ia3andy opened this issue Oct 16, 2024 · 1 comment
Open

Qute includes resolution is not intuitive and can be confusing #43907

ia3andy opened this issue Oct 16, 2024 · 1 comment
Labels
area/qute The template engine kind/enhancement New feature or request

Comments

@ia3andy
Copy link
Contributor

ia3andy commented Oct 16, 2024

Currently when using includes we might have the feeling that we are dealing with paths because include intuitively refer to including other files. In Qute case were are (in the current state) dealing with ids.

For example this doesn't work even if they are located in the same directory:
templates/foo/bar.html

{#include baz.html}

templates/foo/baz.html

In Qute next we should think about having a path like resolution for templates (or using another keywork like {#partial .../} which doesn't refer to file)

@quarkus-bot quarkus-bot bot added the area/qute The template engine label Oct 16, 2024
@quarkus-bot
Copy link

quarkus-bot bot commented Oct 16, 2024

/cc @mkouba (qute)

@geoand geoand added the kind/enhancement New feature or request label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qute The template engine kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants