-
Notifications
You must be signed in to change notification settings - Fork 31
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
Feature/table #2593
base: main
Are you sure you want to change the base?
Feature/table #2593
Conversation
…d-react into feature/table
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dette blir bra! 🚀
Co-authored-by: Camilla Marie Dalan <[email protected]>
- Makes refactoring the app framework a lot harder. | ||
- Leads to unclear interfaces between UI components and the app framework. | ||
- Makes developing UI components complex without deep understanding of the application. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Enables sharing of pure components (docs, Studio, ???) |
?
As ADRs are introduced here, it would be convenient to add the template.md file to the adr folder 🙌 |
|
||
- Makes it hard to do component testing outside a fully rendered app. | ||
- Makes refactoring the app framework a lot harder. | ||
- Leads to unclear interfaces between UI components and the app framework. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to have linked examples of code/components for some of these points, I'm sure you've discussed and looked at tons of examples here to inform this assertion but for myself presently and future readers it would be helpful to know the context here 😄
A list of decision drivers. These are points which can differ in importance. If a point is "nice to have" rather than | ||
"need to have", then prefix the description. | ||
|
||
- B1: UI components should only receive data to display, notify the app when data is changed, and notify validity of user input. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- B1: UI components should only receive data to display, notify the app when data is changed, and notify validity of user input. | |
- B1: UI components should only receive data to display, and notify the app when data is changed. |
I suggest that we remove the validation of user input part, as it makes little sense to leave this to UI components in our context
Description
Related Issue(s)
Verification/QA
kind/*
label to this PR for proper release notes grouping