Qute includes resolution is not intuitive and can be confusing

[ia3andy]

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[bot]]

/cc @mkouba (qute)

[mkouba]

In Qute case were are (in the current state) dealing with ids.

Yes, in Qute we use template ids which are absolute/full paths for file-based templates located in src/main/resources/templates. But it could be anything really. I personally don't think it's a big problem because the paths are usually not very long and it's IMO sometimes better to see the "full path" instead of things like ../../foo.html, especially when you have some nested includes/tags 🤷.