Skip to content
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

Consider adding higher-order components for visibility of e.g. action buttons. #2659

Open
Macroz opened this issue May 6, 2021 · 0 comments
Labels
Technical Debt Improving internal product quality
Milestone

Comments

@Macroz
Copy link
Collaborator

Macroz commented May 6, 2021

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.

@Macroz Macroz created this issue from a note in Rems task board (Ideas) May 6, 2021
@Macroz Macroz added the Technical Debt Improving internal product quality label May 6, 2021
@Macroz Macroz added this to the UI Refresh milestone Mar 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Technical Debt Improving internal product quality
Projects
Development

No branches or pull requests

1 participant