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
When using the q-header tag in HTML I get a UndefVarError: q__header not defined error. This is expected as QHeader is not part of StippleUI.
However, if I interpolate <% quasar(:header) %>, then the header works. This is confusing as the interpolation should inject the <q-header></q-header> tags into the HTML code.
The situation is a bit different. When we use StippleUI to implement any element, the result type is ParsedHTMLString. This type indicates to the parser that the code does not need to be parsed before rendering. So your ui_interp() contains a layout element, which will not be parsed. If you'd pipe your ui content to ParsedHTMLString, you won't see any error:
When using the
q-header
tag in HTML I get aUndefVarError:
q__headernot defined
error. This is expected as QHeader is not part of StippleUI.However, if I interpolate
<% quasar(:header) %>
, then the header works. This is confusing as the interpolation should inject the<q-header></q-header>
tags into the HTML code.Here's a MWE to test this:
Looking at the code here,
I assume that
quasar
registers theq__header
tag and so there is no error when loading the page.Should we autoregister q-tags and throw a warning instead of an error when there's tags unsupported by StippleUI?
The text was updated successfully, but these errors were encountered: