Skip to content
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

Upgrading from 1.5 to 2.4 is causing some troubles #344

Open
stijlfigurant opened this issue Oct 6, 2015 · 3 comments
Open

Upgrading from 1.5 to 2.4 is causing some troubles #344

stijlfigurant opened this issue Oct 6, 2015 · 3 comments

Comments

@stijlfigurant
Copy link

I have a project that was using 1.5 and we felt it was time to upgrade. Am aware of the breaking changes and have handled those.

Added js-data & js-data-angular to the project and injecting it as 'js-data'.

Thrown error is:

TypeError: b.getEndpoint is not a function
    at b.e.value (application.js:10640)
    at b.e.value (application.js:10640)
    at application.js:10626
    at application.js:10429
    at n.a.$get.n.$eval (application.js:10443)
    at n.a.$get.n.$digest (application.js:10440)
    at n.a.$get.n.$apply (application.js:10443)
    at application.js:10330
    at Object.e [as invoke] (application.js:10349)
    at d (application.js:10329)

Tried adding in the js-data-http dependency, which resolved this issue, but causing issue further down the line as it doesn't pick up the interceptors that we push into $httpProvider, which makes sense. But we also would like to stick to $httpProvider as we're $http at a few places elsewhere in the project.

Maybe I am missing some configuration specifics, but the documentation is not giving me the right hints.

@jmdobry
Copy link
Member

jmdobry commented Oct 6, 2015

The latest js-data is v2.5.0, the latest js-data-angular is v 3.1.0. Use those.

@stijlfigurant
Copy link
Author

Hi @jmdobry thanks for the reply.

We actually tried these versions as well, the exact same problem occurs.

@jmdobry
Copy link
Member

jmdobry commented Oct 6, 2015

In that case, can you create a plunker that demonstrates the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants