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
Currently some top level container component does the logic, and passes a can-xxx? parameter to a view component. Some of these could be automated / made a pattern. We trust the text component, which is not actually a purely functional view component, to be used inside other "purely functional view components". Following the same logic we could have our own framework-y higher-order components that help in implementing our common "is component visible to this role" or "is action enabled here" type of situations.
The text was updated successfully, but these errors were encountered:
Currently some top level container component does the logic, and passes a
can-xxx?
parameter to a view component. Some of these could be automated / made a pattern. We trust thetext
component, which is not actually a purely functional view component, to be used inside other "purely functional view components". Following the same logic we could have our own framework-y higher-order components that help in implementing our common "is component visible to this role" or "is action enabled here" type of situations.The text was updated successfully, but these errors were encountered: