-
Notifications
You must be signed in to change notification settings - Fork 841
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
[Tech debt] Create new internal util for rendering semantic <a>
/<button>
elements
#7533
Conversation
aa22fce
to
c2c3a88
Compare
- all logic is related to links, and I'm shortly about to add some DRY logic that is link adjacent but not security adjacent that will use these utils, so it feels like it makes sense to group them all together
- and update component imports
- gets slightly messed by the new component, we need to semi-brute-force it
+ migrate Enzyme tests
c2c3a88
to
936b098
Compare
- the component will now automatically detect this
936b098
to
3d3453d
Compare
Preview staging links for this PR:
|
💚 Build Succeeded
History
|
👋 Hey there. This PR hasn't had any activity for 90 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
🙈 Still working on this, I want to pick it back up after the Emotion meta |
👋 Hey there. This PR hasn't had any activity for 90 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
Someday...... |
Closing, won't have time to finish this sadly. |
Summary
This is a setup PR.
NOTE: No functional output DOM should have changed as a result of this PR, it's purely meant to DRY out repetitive logic and help clean up confusing types as a result.
QA
General checklist
- [ ] Checked for accessibility including keyboard-only and screenreader modes