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
Bug 1841025: Disable linkify fuzzy links #5800
Conversation
@TheRealJon: This pull request references Bugzilla bug 1841025, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
children, | ||
fuzzyEmail = true, // recognize emails without mailto: prefix. Default true. | ||
fuzzyIP = false, // allow IPs in fuzzy links above. Can conflict with some texts like version numbers. Default false. | ||
fuzzyLink = true, // recognize URL-s without http(s):// head. Default true. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to just turn this off entirely (or at least default to false). I suspect we will have the same problem in other contexts with image pull specs.
fuzzyIP = false, // allow IPs in fuzzy links above. Can conflict with some texts like version numbers. Default false. | ||
fuzzyLink = true, // recognize URL-s without http(s):// head. Default true. | ||
}) => { | ||
linkify.set({ fuzzyEmail, fuzzyIP, fuzzyLink }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this will work correctly. This is setting the global configuration. If there are two components with different configuration, you don't know what you'll get.
@spadgett We could disable the |
I'm not sure what we can do about that except not linkify :/ Are there any common cases you're aware of where this happens? I'd vote for just disabling |
Only linkify url strings that begin with a protocol scheme.
@spadgett Updated according to your feedback. Sorry, this kinda fell off my radar 😆 |
@TheRealJon: This pull request references Bugzilla bug 1841025, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spadgett, TheRealJon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@TheRealJon: All pull requests linked via external trackers have merged: openshift/console#5800. Bugzilla bug 1841025 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Only linkify url strings that begin with a protocol scheme.