bcgov / bcgov/entity

UI Tech Debt - Making folio component consistent throughout the application.

Open
#16,867 2 comments 0 reactions 0 assignees View on GitHub
Assets techdebt UX Assurance
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

## What is the problem?
* We have different design requirements for folio components, and I was wondering if we want to make them the same. To improve consistency throughout the application.

In ppr flows and confirm mhr search, we cap the folio at 50 characters, and display a different character validation message. As well as do not highlight the label.

![image.png](https://images.zenhubusercontent.com/64515127b0af5d4f4e13a48f/ca6d0a39-c930-4b70-926c-ce53889e8cd6)

Well in the mhr manufacturer registration flow. We cap the characters at 30, highlight the label.

![image.png](https://images.zenhubusercontent.com/64515127b0af5d4f4e13a48f/1cbe61b5-d578-4b4b-9c8a-213aeebeb8bb)

## What is the impact?
* Improves consistency throughout the application

## Proposed solution
* Very simple refactoring, only 1 - 2 story points.
- Update folio to allow up to 50 characters (note: this will be truncated to 30 when sent back to DB2)
- Validation should be updated to remove word "reached" in all PPR and MHR flows
- Update Folio to red in error state
- Updates needed in PPR/MHR Search Folio and MHR folio shown above
- Ensure intro text stays correct for the different applications

![image.png](https://images.zenhubusercontent.com/5ba90c7629a785544981da1c/07d5e25c-f5f6-444c-bf72-8ab343a22d52)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.