Wrong $resource URL when parameter is int==0

[bonya]

If resource.userId === 0

$resource('/users/:userId/', {}, {save: {method: 'POST'}}).$save() 

calls the wrong url '/users' instead of '/users/0' since userId === 0 is treated as false during uri segment encoding.

I believe it should be checked agains 'undefined' and null instead.

Version 1.0.1
File: angular-resource.js (292)
encodedVal = encodeUriSegment(params[urlParam] || self.defaults[urlParam] || "");

[benjamine]

I ran into this issue too, I'm sending my fix as pull request

[jakecar]

There was either a regression, or this issue was not fixed for parameters within the URL string.

http://jsfiddle.net/7XyKh/27/

• In the first link, for parameter 1, the GET query is "http://search.twitter.com/search.json/1?callback=angular.callbacks._0" as expected
• In the second link, for parameter 0, the GET query is "http://search.twitter.com/search.json?callback=angular.callbacks._1" when it should be "http://search.twitter.com/search.json/0?callback=angular.callbacks._1"!