I've seen these calls:
$location.url('/path/to/something/' + id + '/index');
and
$location.path('/path/to/something/' + id + '/index');
It seems they are doing the same thing.
From documentation I've found that URL is eg /path?a=b#hash
, and path is a part of URL.
Is there any difference which of these setters to use ( $location.path
or $location.url
) in case of the same argument?
$location.path
returns the part of the URL after the slash NOT including search string parameters (after the question mark)
$location.url
returns the entire URL after the slash, including search string parameters.
For example, let's say you have this URL
http://example.com/#/some/path?foo=bar&baz=xoxo
$location.url
returns /some/path?foo=bar&baz=xoxo
$location.path
returns /some/path
These two functions act as both setters
and getters
.
Url
is basically Path + search strings
. In your case, there are no search parameters, so both of them will return the same thing.
$location.path()
allows you to extract out a specific part of your depending on your search string after the slash and excluding the parameters I guess. And if you don't have a search string then it works the same way as the $location.url()
method does.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.