If you have a detailed hypothesis with various links to UI specs or tech docs or whimsical GIFs, the text appears as plain text (with linebreaks removed, see #4017), meaning you need to scan the text, manually copy links (like a chump) and then open a new tab, paste the text link to see the content.
There should be several npm modules which auto-link text (linkify-urls or linkify-it or probably dozens of others), and I'm sure PyPI has some too, depending on where the logic would need to be injected (but probably best to do it at render time vs preprocessing).
If you have a detailed hypothesis with various links to UI specs or tech docs or whimsical GIFs, the text appears as plain text (with linebreaks removed, see #4017), meaning you need to scan the text, manually copy links (like a chump) and then open a new tab, paste the text link to see the content.
There should be several npm modules which auto-link text (linkify-urls or linkify-it or probably dozens of others), and I'm sure PyPI has some too, depending on where the logic would need to be injected (but probably best to do it at render time vs preprocessing).
Ref: https://stage.experimenter.nonprod.dataops.mozgcp.net/experiments/nimbus/lorem-ipsum-hypothesis-test/request-review
┆Issue is synchronized with this Jira Task ┆Issue Number: EXP-610