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 Sep 24, 2021. It is now read-only.
Currently a layout component (Denoted with @Layout decorator) can have a state on the frontend. It inherits from Component and its markup is subject to the same templating binding and reactivity that any other component is subject to.
The problem arises around server side rendering pages that use a layout which has data. The component should append its inherited layout parameter to its own parameters.
Currently a layout component (Denoted with
@Layout
decorator) can have a state on the frontend. It inherits fromComponent
and its markup is subject to the same templating binding and reactivity that any other component is subject to.The problem arises around server side rendering pages that use a layout which has data. The component should append its inherited layout parameter to its own parameters.
Issue is around:
prism/src/component.ts
Line 677 in 9f76e8b
There is also a opportunity here to refactor the way client global parameters work in the same way.
The text was updated successfully, but these errors were encountered: