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

Remove v6 and backwards compatibility with GOV.UK Elements #1123

Closed
wants to merge 2 commits into from

Conversation

fofr
Copy link
Contributor

@fofr fofr commented Oct 22, 2021

Remove v6 backwards compatibility with GOV.UK Elements. GOV.UK Elements is deprecated and has not been released since July 2018. New prototypes should be using the GOV.UK Design System.

Fetch upstream to remove-v6
Copy link

@paulrobertlloyd paulrobertlloyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love this! I delete these things every time I start a new prototype.

package.json Show resolved Hide resolved
GOV.UK Elements has not been released since July 2018.
New prototypes should be using the GOV.UK Design System.
@joelanman
Copy link
Contributor

this is something I've considered, is it causing any issues other than downloading code you don't need?

@fofr
Copy link
Contributor Author

fofr commented Oct 22, 2021

From a x-gov Slack thread:

It’s more of a question of – why is it still here – why is the use of deprecated packages like elements and toolkit still being supported?

I think the crossover of users pulling the latest kit to update their prototypes and users still stuck on elements is going to be tiny.

Also, the upgrade path for a prototype created from a ZIP file is usually updating the dependencies in package.json, rather than re-applying commits from the base repo.

@joelanman
Copy link
Contributor

joelanman commented Nov 3, 2021

Thanks for this. Unfortunately this is not a priority for us at the moment. We do want to look into tidying up the kit and removing things people don't need as a body of work, but it's not our focus at the moment. When we do it we'd need to check who is affected and how to communicate the changes to them.

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

Successfully merging this pull request may close these issues.

3 participants