js-data/js-data-http

Adapter default basePath is taken instead of definition basePath

ScottTrenda opened this issue · 4 comments

ScottTrenda commented

If basePath is defined on an adapter's defaults, then it is used for resolving all paths before a resource's basePath is referenced.

Basically this is the same issue as js-data/js-data#232 (and should have the same fix), but it pervades into js-data-angular, and occurs over a much larger set of instances.

crobinson42 commented

@ScottTrenda v2.2.3 published ☝️ thx again. We're not going to be doing any more work on v2 so I recommend you upgrade to v3 asap 👍

ScottTrenda commented

Awesome, thank you. Could I please request a patch release of js-data-angular that uses js-data-http v2.2.3? Much appreciated!!

crobinson42 commented
ScottTrenda commented

I can try. It looks like v3.2.0 to v3.2.1 is just a simple upgrade of js-data-http to v2.2.2, so I'll take a look at what went into that and do the same.