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.

Sign up for GitHub

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

Jump to bottom

How should a user edit a single element in a complex form component. #1200

Closed
4 tasks
Febakke opened this issue Mar 4, 2019 · 1 comment
Closed
4 tasks

How should a user edit a single element in a complex form component. #1200

Febakke opened this issue Mar 4, 2019 · 1 comment
Labels
area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. kind/user-story Used for issues that describes functionality for our users. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. status/wontfix Status: Used when something will not be fixed. Describe why.
Milestone
2022

Comments

@Febakke
Copy link
Member

Febakke commented Mar 4, 2019

Description
As a user i would like to only make "postnummer" read-only in the "adresse" component.

When we get more complex components in the ui-editor we need to find a way to handle child elements within the component.

(Complex components as in components made out of two or more components. "adresse" component is an example)

Sketch (if relevant)
(Screenshot or link to Figma, make sure your sketch is public!)

Technical considerations
Input (beyond tasks) on how the user story should be solved can be put here.

Acceptance criterea

  • What is allowed/not allowed (negative tesing)
  • Validations
  • Error messages and warnings
  • ...

Tasks

  • Find a way to select elements in complex components
  • Design how the view in Altinn Studio
  • Write acceptance criterea
  • Make tasks for development
@Febakke Febakke added area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. kind/user-story Used for issues that describes functionality for our users. team-tamagotchi labels Mar 4, 2019
@helenekri helenekri mentioned this issue Mar 4, 2019
Closed
16 tasks
@lvbachmann lvbachmann added this to the Post-MVP milestone Mar 7, 2019
@malmil malmil added status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. and removed needs-specification labels Mar 14, 2019
@GGunnar GGunnar modified the milestones: Post-MVP, CD - phase 3 Oct 8, 2019
@lvbachmann
Copy link
Contributor

Complex form components was a dead end. To be handled as widgets going forward. Swapping the existing complex component to a widget is handled by Altinn/app-frontend-react#289

@lvbachmann lvbachmann added the status/wontfix Status: Used when something will not be fixed. Describe why. label Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. kind/user-story Used for issues that describes functionality for our users. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. status/wontfix Status: Used when something will not be fixed. Describe why.
Projects
None yet
Milestone
2022
Development

No branches or pull requests
4 participants
@Febakke @lvbachmann @malmil @GGunnar