[Feature Request]: URL field type #1140
Description
Checklist
- I am using an up-to-date version.
- I have read the documentation.
- I have searched existing issues.
Description
As was brought up in #924, it would be a good idea to add a dedicated URL field type, rather than having links be embedded in text fields (though, both could coexist if needed). This would remove the reliance on a regex pattern for detecting URLs (which can never be completely perfect), and allow the user to specify what is and isn't a URL.
Solution
A URL field type could be added, which functions nearly identically to a text field, but will interpret all content as a URL (even if it isn't a valid URL). This could allow for more niche URL types to be embedded, such as URLs with non-HTTP/HTTPS protocols (for my use case, it would be very helpful to be able to embed discord:// links).
These fields could potentially also provide functionality for naming the URL, which would be displayed in place of the URL itself.
Alternatives
#924 works well for most common cases, but as mentioned in the discussion, isn't perfect, and will miss plenty of valid URLs. In my opinion, it's better to add a new URL field type and leave the decision of what is and isn't a URL up to the user.