We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have run into this issue before here: #1310
This seems to be a problem for other components too, you can see the impact live on GOV.UK: https://www.gov.uk/register-to-vote
You can reproduce this by going to: http://localhost:3000/components/button/start-link/preview?legacy=1
And changing the href to something unique in the example yaml file.
This may be an issue with other components too.
The text was updated successfully, but these errors were encountered:
Not sure if there's a more holistic approach we can have here.
Should all hrefs get automatically be cache busted?
If we did that how do we test visited states?
Sorry, something went wrong.
NickColley
Successfully merging a pull request may close this issue.
We have run into this issue before here: #1310
This seems to be a problem for other components too, you can see the impact live on GOV.UK: https://www.gov.uk/register-to-vote
You can reproduce this by going to:
http://localhost:3000/components/button/start-link/preview?legacy=1
And changing the href to something unique in the example yaml file.
This may be an issue with other components too.
The text was updated successfully, but these errors were encountered: