COOPS-UI: update to latest common components

[severinbeauvais]

Description:

Coops UI is using an older version of the sbc-common-components and is therefore missing some fixes and new functionality.

I created this ticket because it's not as simple as updating the dependency version in package.json -- since other common components may have changed, the coops-ui code may need to be updated also. In particular, the following need to be tested:

• base address
• header / login / logout / return to upper page
• footer
• token services

Dependencies This ticket is all about Coops UI using the latest sbc-common-components dependency.

Acceptance Criteria

• We get the latest common features.
• Coops-ui components continue to function normally.
• New features are either available and usable, or they are hidden and new tickets are written to enable them. (Please diff sbc-common-components between v22 and v30 to identify any changes.)

Validation Rules See AC.

Ready for Sprint (DoR)

• [ ] Do we have a prioritized Sprint backlog?
• [ ] Defects, user stories and other work the team has committed to are contained in the sprint backlog?
• [ ] Any hidden work?
• [ ] All team members availability & capacity is known for the sprint?
• [ ] All users stories meet the definition of Ready?

Ready to Build, Story level (DoR):

• [ ] Have Stakeholders approved this story?
• [ ] Does User story have full flow of business rules, happy and alternate paths etc. ?
• [ ] Are the dependies known/understood?
• [ ] Dev team accepts user experience artifacts?
• [ ] Are the validation rules defined? (UI, Data, Role-Action)
• [ ] Is a formal UAT required for this user story?
• [ ] Are the acceptance criteria well defined in this ticket (Story level) that QA can confirm or deny ?
• [ ] Does user story need to reference BA checklist? ( are functional/Non functional descriptions captured ?)
• [ ] Is the person who accepts this user story as complete identified? (PO)
• [ ] Can this User story be sized by the Dev. team ?
• [ ] Can this User story be demoed to show value?
• [ ] Is this user story small enough to be completed in a sprint?

Acceptance / DoD:

• [ ] 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
• [ ] All Linters passed
• [ ] 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
• [ ] UX Approved
• [ ] PR Accepted
• [ ] Production burn in completed

[WaldemarSchneider86]

~~Severin mentioned 2019-12-23 that it is not critical not to be in Release Jan. 10. Will be done later. Agreed w. team in "Team Sprint Review". ~~

Update by SB: Cameron and I have decided to repurpose this ticket (and I have already updated the description accordingly) and are planning to include it in the forthcoming release (2.4.0 on Jan 10).

[severinbeauvais]

Quick status update: coops-ui was using sbc-common-components v2.0.22. Now we want to use v2.0.30. However, about a third of our Jest unit tests report an error transpiling the code in the new version. (I found that v23 is fine but when I update to v24 the tests break.) So far I have not been able to determine any real difference between v23 and v24. Cameron said he'd have a quick look at it.

NB I have checked in some package dependency updates (and corresponding lint fixes) in this branch: https://github.com/severinbeauvais/lear/commits/1984.

[severinbeauvais]

Cameron fixed the Jest issue and will be PRing the changes for this ticket.