Modularize and update layout of Certify Correct Component
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Background**
This ticket was created to add some additional changes to [#1550](https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/1550), updating the certify statement.
**Description**
* Users will see a new layout of the certify component when completing a filing. (see scott's linked design ticket)
* Users will see different text in the "instructional text" underneath the header of the component "Certify Correct"
> Enter the name of the current director, officer, or lawyer submitting this **[FILING TYPE]**
At the PR:
DoD - for all User Stories:
- [ ] PR to remove feature flags created
- [ ] Check Requirements against completed stories
- [ ] Completed stories verified in Dev/Test/Prod
- [ ] Confirm Test cases built and succeeding
- [ ] Confirm successful End-End runs
- [ ] No regression
- [ ] Test coverage and Test ID acceptable by Product Owner
- [ ] Ticket merged to master or story branch
- [ ] Add / maintain selectors for QA purposes
- [ ] Add PR numbers - If available
- [ ] All tests passed (Jest, Pytest, Postman)
- [ ] Developer to list Config changes/ Update documents and designs
- [ ] Design / Solution accepted by Product Owner
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Test coverage acceptable
- [ ] Peer Reviewed
- [ ] Accessibility reviewed and acceptable [checklist](https://github.com/bcgov/entity/docs/coding-standards/accessibility.md)
- [ ] UX Approved
- [ ] PR Accepted
- [ ] Production burn in completed
- [ ] Must include automated unit tests
- [ ] Must include integration tests that run in a pipeline
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.