Closed guarmo closed 1 week ago
Latest commit: 585f6ef77e9e02e98ef19313fffc535ed23ab52f
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Name | Link |
---|---|
Latest commit | 585f6ef77e9e02e98ef19313fffc535ed23ab52f |
Latest deploy log | https://app.netlify.com/sites/tiptap-embed/deploys/672b786a9e12930008b52c20 |
Deploy Preview | https://deploy-preview-5808--tiptap-embed.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@guarmo I can't afford to look into this carefully right now, but does this PR implement the proposed solution by @nperez0111 mentioned here (an older PR that aims to fix the same issue).
What about backward compatibility? For example, what if someone previously only wanted to autolink URLs starting with https://
. They may have added a validation function like:
validate: url => url.startsWith('https://),
With the current change, only URLs starting with https:// would be valid, which is not the same behavior as before.
What about backward compatibility? For example, what if someone previously only wanted to autolink URLs starting with
https://
. They may have added a validation function like:
validate: url => url.startsWith('https://),
With the current change, only URLs starting with https:// would be valid, which is not the same behavior as before.
Yep, you are totally right here. Good catch, will have to look into how it can be kept backwards compatible
Changes Overview
Added a new
shouldAutoLink
function to control the auto-linking of URLs based on specific criteria, such as disallowed domains, and enhanced the existingvalidate
function to handle URLs more robustly.Testing Done
Checklist
Related Issues
5564