extract url parsing / composing into reusable service

[vojtajina]

something like this:

compose(/path/:verb, {verb:'greet', salutation:'Hello'});
// results in URL /path/greet?salutation=Hello

$route does similar (reverse) stuff when parsing an url into params...

[witoldsz]

+1 :)

[m6w6]

+1

[niklasbulitta]

+1

[bsr203]

+1

[iwein]

This is a nice idea, would it be a good idea to expose this service on $location and also allow parsing of url strings without actually changing the location (if you pull one from an iframe for example)?

[georgiosd]

+1

[dmitryevseev]

+1

[tanepiper]

+1 would love to see something as powerful as http://medialize.github.com/URI.js/ rolled into $location

[snichme]

+1

[brettlaforge]

+1

[coli]

+1, one of my template needs this right now to massage some urls

[Leksyk]

+1

[eyelidlessness]

+1

[pahlers]

I would like to have this. It can't be difficult to implement. $resource has the same system (Route.setUrlParams).

[pahlers]

Made some code to solve this problem. It would be better when this was native angular code.

https://github.com/eonlepapillon/parametrizedLocation

[ralphschindler]

👍

[celmaun]

+1

[bsr203]

I have been using https://github.com/fxa/uritemplate-js
uses like,
template = UriTemplate.parse('{?query*})'; template.expand({query: {first: 1, second: 2}}); --> "?first=1&second=2"

it is based on RFC6570

Another popular one is https://github.com/medialize/URI.js
better docs, and option http://medialize.github.io/URI.js/

the only issue is the RFC uses {id} format, and angular :id. That's actually ok, depends on how you represent your string url. You can use it in route registration too like

$routeProvider .when(UriTemplate.parse('/path/{verb}).parse({}) ...
`

[gauravmeena0708]

+1

[sodacrackers]

1+

[johncrim]

+1

URL is not a standard javascript class, so this really should be a core angular service, to avoid many duplicates of similar logic.

[STOpandthink]

+1

[tools4origins]

+1

[andy-rush]

+1. Or more.

[chetankhilosiya]

+1
The valid use case I have is, I need to check the length of url generated for GET request before making request, as some urls generated are too long due to request params has list that grows big.

[pashchuk]

Is there any progress on this one?

[panlina]

+1

[petebacondarwin]

OK, so we have agreed to expose the setUrlParams function as a service on the ngResource module. We do not want to add it to the core AngularJS module as it would add unnecessary code to that file.

[Narretz]

We've decided not to add this after all, as only a small number of people would benefit from the option to manipulate url params in resource. And we don't want to expose a general url composition service in AngularJS as core should cater specifically to the needs of the framework.

[petebacondarwin]

@gilbsgilbs - since we are entering LTS mode the code for manipulating the URLs internally in AngularJS is not going to change (or at least it is very very unlikely to change). So it is pretty easy and safe to copy the code from angular-resource.js and reuse it in your own applications.

[gilbsgilbs]

@petebacondarwin that's a neat suggestion. Thank you very much. I will opt for this (and I totally understand the decision).