Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IOAPPX-467] Remove legacy color palette #384

Merged
merged 7 commits into from
Jan 30, 2025

Conversation

dmnplb
Copy link
Collaborator

@dmnplb dmnplb commented Jan 24, 2025

Short description

This PR completely removes the legacy colour palette, except for the primary blue colour, which is still needed to render the legacy UI in the most appropriate way.

List of changes proposed in this pull request

  • Remove the legacy color palette
  • Rename blue to blue-500
  • Leave the legacy color set with the different shades of blue-500 (blue-600 and blue-50)
  • Update tests and snapshots
  • Remove two legacy pictograms that were left for legacy support

How to test

Run the example app and check if everything is okay

@dmnplb dmnplb merged commit 85cf07e into main Jan 30, 2025
6 checks passed
@dmnplb dmnplb deleted the IOAPPX-467-remove-legacy-color-palette branch January 30, 2025 09:36
github-merge-queue bot pushed a commit to pagopa/io-app that referenced this pull request Jan 31, 2025
> [!important]
> This PR depends on the following:
> * pagopa/io-app-design-system#384

## Short description
This PR completely removes the legacy color palette, except for the
primary `blue` color, which is still needed to render the legacy UI in
the most appropriate way.

## List of changes proposed in this pull request
- Replace all the legacy color values with the new ones
- Update `io-app-design-system` to `4.5.1` and relative `jest` snapshots

## How to test
Run the application and navigate through the screens and sections to
make sure that everything looks and feels right.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants