-
Notifications
You must be signed in to change notification settings - Fork 476
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
won't parse domains #115
Comments
I'm sorry, but I don't understand the issue. are you calling URI('/').search('google.com').toString() === "/?google.com"; |
No the literal string 'google.com'. Is not parsed. Ignore the search that was just the context of my string. -- Anthony On Sep 7, 2013, at 1:32 AM, Rodney Rehm notifications@github.com wrote:
|
I can see your problem now. In order to have an authority parsed as such, you need to add the protocol separator URI('google.com').path() === 'google.com';
URI('//google.com').domain() === 'google.com'; This is not a bug. This is ambiguity at its best… :( |
I was actually trying this code with 'google.com' and it failed to recognize a url.
|
Ok, so you're talking about The regular expression used to extract URIs from text expects a URI to either begin with a protocol (e.g. |
search (google.com)
this string fails.
The text was updated successfully, but these errors were encountered: