-
Notifications
You must be signed in to change notification settings - Fork 27.5k
Respect PORT from URL without escaping #2652
Conversation
Allows to write urls normally.
This is an interesting idea. What you are saying is that since parameters cannot be identified as a number, then any parameter starting with a colon and only containing digits (e.g. I like this. @IgorMinar - is there any reason why this should break previous functionality? |
PR Checklist (Minor Feature)
|
@@ -106,6 +106,13 @@ describe("resource", function() { | |||
R.get({a: 'foo', b: 'bar'}); | |||
}); | |||
|
|||
it('should support por unescaped url', function() { |
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.
typo : "por" -> "an"
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.
My bad. This is to be fixed.
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.
it('should support unescaped port in url'), function() {
Is this better?
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 think it should be "should support an unescaped port in url"
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.
@petebacondarwin My full name is Leandro Ostera Villalva. |
This PR has moved to #2778 |
Allows to write a URL normally.
Escaping the port does not comply with the URL syntax
Regular Expression and it's position in the if clause are meant to short-circuit ASAP.