Kyse

Hmm, initial thought would be turn off persistence and test again. Perhaps I did some bad stuff with it. But your tests are just creating a new odataresource object, not...

I added in a resourceStore to capture existing settings for the odataAngularResource, so allow providing a way to expose in the promise chain a way inject corrective measures for errors....

Just want to write a quick update. I been very busy with work, but I have not forgotten about needing to look into this.

Was just reviewing this after running into a case with it myself. Looks like the suggested fix would probably break the case where the is embedded in the url (ie...

If one hasn't been created yet, I'd suspect you'll have to wait for OData webapi to finish up their aspnetcore 2.0 port. They've just started releasing alpha builds.

He's pretty willing to merge PR's if you've got the time to add the functionality. Generally just need to make sure unit tests are written up to serve as examples...

I've run into a situation where this would probably help me out. Care to discuss some thoughts on how you'd picture it working? Going to do some thinking out loud...

Some libraries (like angular grids) work well and expect the resource object and know how to check resourceObj.$promise to know when resourceObj array will be populated and to populate the...

You'll have to be a little more detailed on what you don't understand about the refresh functionality. Or "forced refresh" for that matter. Please refer to the [Refresh Section](https://github.com/devnixs/ODataAngularResources#refreshing-responses--odata-query-persistence) for...

Your code looks right to me. Have you taken a look at the unit teats for other examples?