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

Feature/table #2593

Draft
wants to merge 32 commits into
base: main
Choose a base branch
from
Draft

Feature/table #2593

wants to merge 32 commits into from

Conversation

adamhaeger
Copy link
Contributor

@adamhaeger adamhaeger commented Oct 17, 2024

Description

  • Adds Table component
  • Introduces component libary
  • Includes ADR describing the propsed change
Screenshot 2024-10-17 at 11 36 08 Screenshot 2024-10-17 at 14 17 44

Related Issue(s)

Verification/QA

  • Manual functionality testing
    • I have tested these changes manually
    • Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
    • No testing done/necessary
  • Automated tests
    • Unit test(s) have been added/updated
    • Cypress E2E test(s) have been added/updated
    • No automatic tests are needed here (no functional changes/additions)
    • I want someone to help me make some tests
  • UU/WCAG (follow these guidelines until we have our own)
    • I have tested with a screen reader/keyboard navigation/automated wcag validator
    • No testing done/necessary (no DOM/visual changes)
    • I want someone to help me perform accessibility testing
  • User documentation @ altinn-studio-docs
    • Has been added/updated
    • No functionality has been changed/added, so no documentation is needed
    • I will do that later/have created an issue
  • Support in Altinn Studio
    • Issue(s) created for support in Studio
    • This change/feature does not require any changes to Altinn Studio
  • Sprint board
    • The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
    • I don't have permissions to do that, please help me out
  • Labels
    • I have added a kind/* label to this PR for proper release notes grouping
    • I don't have permissions to add labels, please help me out

Copy link
Contributor

@cammiida cammiida left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dette blir bra! 🚀

adr/001-component-library.md Outdated Show resolved Hide resolved
- 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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Enables sharing of pure components (docs, Studio, ???)

?

@HauklandJ
Copy link
Contributor

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.
Copy link
Contributor

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New Table component
6 participants