-
Notifications
You must be signed in to change notification settings - Fork 64
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
Tidy up unused files #702
Comments
Is this not a dupe of #376? |
no this is more a check everything and remove anything that is not being used issue. A tech debt tidy up. Which depending on its size may end up being split up. |
This issue's very vague is all. We already have a deprecated issue label for stuff not covered in #376. Maybe we should link to all those in this issue instead? |
Good point, I have updated the description
In my mind this is associated with deprecated CSS and JavaScript from when the component library work was initially created
This is hard dependancies and potentially is deprecated itself if we are taking a component by component approach |
Legacy stuff will be removed as part of the v4 work |
Once we have the belts and braces of Visual Regression tests running on the component library there appears to be a lot of files and folders that are not in use inside
assets-frontend
.This unused work can then be removed safely, with a level of confidence that it won't cause undesired knock on effects.
The text was updated successfully, but these errors were encountered: