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
{{ message }}
This repository has been archived by the owner on Jan 21, 2023. It is now read-only.
I tried to generate modules and pages with passing --folder parameter.
yo yeogurt:template components --folder=base --type=module
which generated the file at client\templates\modules\base\components.swig.
but in generated swig file, metadata to link it to dashboard creates entry as follows.
"link": "generated/base//components.html"
Same goes for page templates
yo yeogurt:template components --folder=base
generates client\templates\base\components.swig with link "link": "../../base//components.html".
Which of course leads to 404 while trying to navigate to page from dashboard.
Also it extends from wrong path {% extends './layouts/base.swig' %}, which would have been correct if file would have been generated at root of templates folder.
The text was updated successfully, but these errors were encountered:
This is definitely a bug. I'm currently working on a new way to handle the folder linking functionality through the sub-generators in the next release. Hopefully that will help solve this issue.
I tried to generate modules and pages with passing
--folder
parameter.which generated the file at
client\templates\modules\base\components.swig
.but in generated swig file, metadata to link it to dashboard creates entry as follows.
Same goes for page templates
generates
client\templates\base\components.swig
with link"link": "../../base//components.html"
.Which of course leads to 404 while trying to navigate to page from dashboard.
Also it extends from wrong path
{% extends './layouts/base.swig' %}
, which would have been correct if file would have been generated at root oftemplates
folder.The text was updated successfully, but these errors were encountered: