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
However the layout wants to be able to use an expression like this with a clear fallback in the case where the page fails to provide the expression. For example, if the page failed to set either, they could default to empty:
<body class="">
</body>
Obviously simple go expressions won't suffice here. Sections serve a very similar role but they are block based, quite verbose, and require a conditional guard. For example, this will not work:
Often a page handler will want to push values up to the layout without defining a full section. For example:
However the layout wants to be able to use an expression like this with a clear fallback in the case where the page fails to provide the expression. For example, if the page failed to set either, they could default to empty:
Obviously simple go expressions won't suffice here. Sections serve a very similar role but they are block based, quite verbose, and require a conditional guard. For example, this will not work:
It feels like pushup should supply a per-request table that supports primitive values, defaulting to the empty value for each.
I could even see pushing this toward a special reserved symbol, with pushup translating this block into the
^p.Get(...)
syntax above:The text was updated successfully, but these errors were encountered: