👋 Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Primer first responder will review it soon.

• 🎨 If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
• ⏩ If this is a PR that includes changes to an interaction, please include a video recording in the description.
• ⚠️ If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.

This looks like a great change, and thanks very much for adding tests!

I think this might be a good opportunity to look at our current tests and add a lot more robustness to them. It's non-obvious from the outset as to why this change causes such as behavioural change, and looking at the existing test suite, I'm not filled with confidence that this wouldn't introduce a regression somewhere (especially around dropping the else clause).

I'm happy for this PR to be merged and shipped but if you have some extra time I think it could be great to add some additional tests of various input where there may be edge cases.

I have added a few more tests related to links. I think we can keep an eye on the changes and see if there is more regression....is there a way to test before shipping?

Thanks for adding these!

We could make this a mode (i.e. add an option to enable the code path) and ship it as a feature flag in dotcom, but I don't think that'll be necessary. If it regresses we can revert and add more testing.