Thanks for your contribution! In order for us to be able to accept it, we ask you to sign our CLA (contributor's license agreement).

CLA is important for us to be able to avoid legal troubles down the road.

For individuals (a simple click-through form):
http://code.google.com/legal/individual-cla-v1.0.html

For corporations (print, sign and scan+email, fax or mail):
http://code.google.com/legal/corporate-cla-v1.0.html

ping??? we need the CLA signed, otherwise we can not merge this in.

I filled the form, few hours after your email.
Let me try it again.

P

2012/9/12 Miško Hevery notifications@github.com

ping??? we need the CLA signed, otherwise we can not merge this in.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/1113#issuecomment-8477652.

any progress on this? thanks.

Hi,
I've electronically signed a CLA few hours after the first post, then resigned it a month ago (after the ping). I just did it again.
The message I got was "Thank you. Your CLA submission will be processed shortly.".
BTW I work for Google and provided the patch during my working hours for business purposes so I'm not even sure a CLA is required. If there is a way to see what happened to my various signed CLAs (were they blocked? rejected? dropped?), I could investigate. Otherwise I cannot do much more...

@lascap could you link to the mentioned e-mail thread for the reference? While the fix is easy enough I'm curious about your use case for this one, would love to learn more.

Hi Pawel, the initial thread was on private email: here's the main part

I'd like to use $resource but with dynamic default params:

var User = $resource('/user', {'group': function() { return $groupService.currentGroup(); }});

....
//modify group in $groupService
....

// so the group is fetched only when I request for the user
user = User.get({'userId': myId}, function() { .... });

LGTM

I rewrote the tests, added docs and landed this as f57f27d