Altinn / Altinn/app-frontend-react
Replace address component with address widget
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 33
- Avg merge
- 6d 23h
- Merged PRs (30d)
- 3
Description
## Description
The address component - being a multi-field component - has some inherent troubles with being flexible enough for the different use cases. After the introduction of widgets, an address widget is believed to be a more relevant option.
## Considerations
We need to find out what to do with form layouts that already use the address component.
## Acceptance criteria
- Two address widgets are available, creating layouts resembling the address component (simple and complex)
- It's no longer possible to add address components to a form layout
## Specification tasks
- [ ] Development tasks are defined
## Development tasks
> Add tasks here
## Definition of done
- [ ] Documentation is updated (if relevant)
- [ ] Technical documentation (docs.altinn.studio)
- [ ] User documentation (altinn.github.io/docs)
- [ ] QA
- [ ] Manual test is complete (if relevant)
- [ ] Automated test is implemented (if relevant)
- [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)
Contributor guide
Research direction
No files or tests are named; start by locating the existing address component and widget implementations and defining the development tasks for their replacement. Done means two address widgets reproduce the simple and complex layouts, address components can no longer be added to form layouts, and any relevant documentation and testing work is completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100