-
Notifications
You must be signed in to change notification settings - Fork 17
Qute Server Side Components Not Discovered #1040
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
Comments
Thanks @akil-rails for having reported the issue. To fix this ussue we need to:
in Line 32 in e2e1510
|
It's not that easy as it seems, the web-component dir is configurable by the user :-/ Not sure how we could fix this... |
It is the same thing for roq application and we hard code those default path. To support user configuration we will need to read application.properties, and we will need to track changes of this file |
Then we should do this, because it's 100% configured: quarkus.web-bundler.bundle.components=true
quarkus.web-bundler.bundle.components.key=main
quarkus.web-bundler.bundle.components.qute-tags=true
the dir is quarkus.web-bundler.bundle.components=true
quarkus.web-bundler.bundle.components.key=main
quarkus.web-bundler.bundle.components.dir=foo
quarkus.web-bundler.bundle.components.qute-tags=true |
Thanks @ia3andy for yourclarification! It is not a trivial issue. |
As per the qute guide, , user defined tags are automatically registered when placed under template/tags, and this works fine.
As per the quarkus-web-bunlder guide, qute components can be placed under src/main/resources/web/components/[name], this also works
The quarkus extension for vs-code however complains for 'missing section helper' when the quarkus-web-bundler guide's conventions are followed (it works when the qute-reference convention is followed) .. Is something to be done to let vscode extension know about these?
Steps to reproduce:
Original discussion - quarkusio/quarkus#45246
Reproducer - https://github.com/akil-rails/watch
@angelozerr
The text was updated successfully, but these errors were encountered: