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

Update all component packages to latest brand-context version #858

Open
5 tasks done
sturobson opened this issue Jan 5, 2023 · 3 comments
Open
5 tasks done

Update all component packages to latest brand-context version #858

sturobson opened this issue Jan 5, 2023 · 3 comments
Assignees

Comments

@sturobson
Copy link
Contributor

sturobson commented Jan 5, 2023

What

Update the version of brandContext for each component in the front-end toolkits.

Why

Before some larger architectural changes to what is Elements we need to make sure all of the current components that are in the front-end toolkits make use of the latest version of the brand context. This will move us towards the single release and allow us to point the front-end toolkits repo on 'maintenance mode'.

Done When

  • update the "brandContext": "^s.s.s" in the package.json for each component in each brand toolkit
  • create a new demo file for each existing component that has a demo folder.
  • test the new demo file against the existing version using this tool
  • update the package.json for the component to a major breaking change (X.x.x)
  • update the history.md to reflect that we have updated the brandContext in the package.json
@sturobson
Copy link
Contributor Author

note: there is a fresh update to the themes (brand context) (#856) that you might want to wait for - or do a find and replace when it's merged.

I don't think there are any actual values that would impact components specifically (there will be from the Cascade of CSS coming from the brand context itself). It should not break anything.

@Sreilys Sreilys self-assigned this Jan 10, 2023
@amyhupe
Copy link
Contributor

amyhupe commented Jan 11, 2023

As #856 is now blocked, this can be picked up again.

@amyhupe
Copy link
Contributor

amyhupe commented Jan 26, 2023

@amyhupe put some time in to plan comms around this with:

  • Alex K
  • Fred
  • Sabrina
  • Heydon
  • Stu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants