feat(comm): extend application update notification component to match new BASE

[alexvcasillas]

COMM-2458 & COMM-2634

Description

When it comes to displaying the user that there’s a mandatory update and that they need to refresh whether they like it or not, we should be using the ApplicationUpdateNotification component provided by Picasso that follows BASE. But this component is not extensible enough and it does not give room for customization as we have various requirements that need to be fulfilled in order to be able to satisfy the requirements that we’re aiming for with the Force Refresh initiative.

How to test

BASE design 👉🏻 https://www.figma.com/file/vVoOW3YNKJkvRV3RAMPF3Y/Talent-Portal-Library?type=design&node-id=4612-37156&mode=design&t=r0mYhMpZA9tD0VjW-0

• Access Storybook
• Check that all of the acceptance criteria in the attached Jira Ticket is met
• CI should be 💚

Screenshots

Before.	After.

Development checks

• Add changeset according to guidelines (if needed)
• Read CONTRIBUTING.md and Component API principles
• Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
• Annotate all props in component with documentation
• Create examples for component
• Ensure that deployed demo has expected results and good examples
• Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
• Self reviewed
• Covered with tests
• Design Specs have reached BASE

Breaking change

• codemod is created and showcased in the changeset
• n/a test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

• @toptal-bot run package:alpha-release - Release alpha version
• @toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅

You are OK with merging this PR and

1. You have no extra requests.
2. You have optional requests.
   1. Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌

You are not OK with merging this PR because

1. Something is broken after the changes.
2. Acceptance criteria is not reached.
3. Code is dirty.

When to comment (neither ✅ nor ❌)

You want your comments to be addressed before merging this PR in cases like:

1. There are leftovers like unnecessary logs, comments, etc.
2. You have an opinionated comment regarding the code that requires a discussion.
3. You have questions.

How to handle the comments?

1. An owner of a comment is the only one who can resolve it.
2. An owner of a comment must resolve it when it's addressed.
3. A PR owner must reply with ✅ when a comment is addressed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0bb1daa

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@toptal/picasso	Major
@toptal/picasso-charts	Major
@toptal/picasso-forms	Major
@toptal/picasso-rich-text-editor	Major
@topkit/analytics-charts	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[toptal-devbot]

Greetings from FX team, @alexvcasillas 👋

Thank you so much for contributing 🙇

We have got high priority ticket generated on our Kanban board so we will do our best to make your experience supreme!

What's next? We will collaborate using this workflow. For you this practically means making sure DONE criteria is met and responding promptly to code review comments 😉

🙏 please, help us improve, rate your contributing experience after merge

[alexvcasillas]

@toptal-anvil ping reviewers

[alexvcasillas]

Note: Until we have the BASE specs for this updated component we should not merge this

[TomasSlama]

Hey @alexvcasillas any update on this?

[alexvcasillas]

Hey @alexvcasillas any update on this?

Yes @TomasSlama , we're going to be working on this in the next sprint :)

[alexvcasillas]

@toptal-anvil ping reviewers

[TomasSlama]

Small comment, that needs to be addressed. I'm also not sure about the actionsAlignment, I want to know opinion about it from my colleagues, I will raise it today on daily, I will let you know

[alexvcasillas]

Small comment, that needs to be addressed. I'm also not sure about the actionsAlignment, I want to know opinion about it from my colleagues, I will raise it today on daily, I will let you know

Hey @TomasSlama I've added that property so we can have some room for flexibility because on the early design of this component, the buttons were alignment on the left on the initial state of the dismissable modal and on the right when the modal becomes undismissable :)

[alexvcasillas]

@toptal-anvil ping reviewers

[dmaklygin]

Left some minor comments

[mkrl]

Thanks for addressing all the suggestions!
I have one final thing that I think should be fixed and then we can merge it 💪

[mkrl]

Nice job 👍