UI Design - Named Amalgamation change of company type
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Given I am filing an amalgamation where a name is being assigned
When I complete the amalgamation application in the modern system
Then I can choose the edit the resulting company type
In the legacy system BC Benefit Companies did not exist. In modern companies may wish to form as a BC Benefit Company, or other type. Design would need to consider changes in the name (some have additional wording), changes in consent (if a name required consent and changes that may require re-approval). Change of type is being implemented for numbered companies first given the lesser complexity.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by reviewing the modern amalgamation application flow and the existing numbered-company type-change implementation; done means supporting selection of the resulting company type while accounting for name wording, consent, and any required re-approval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100