You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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
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)
The text was updated successfully, but these errors were encountered: