New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collection.fetch : url option is inconsistent in 0.9.2 and 1.0 ? #2578
Comments
Yep yep. Thanks for pointing it out @pierre-duchesne. :) |
Thanks for your help :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have done an upgrade of my application from 0.9.2 to 1.0.
Before this upgrade i could use collection.fetch({url : anUrl}) to change the url of the collection only for this request.
Now, in 1.0, the url of the request is always good but i have a side effect : url attribute of the models, which are created by this request, is equals to the option url of the fetch.
So all the future requests with these models are false (even if urlRoot is defined in the model).
This comportment is normal ?
How to customize the url only for 1 request ?
Thanks in advance
The text was updated successfully, but these errors were encountered: