-
Notifications
You must be signed in to change notification settings - Fork 730
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
Nested REST APIs #409
Comments
Hi spfjr, We're relying on Restangular for that, and I'm not sure it allows to modify the URLs as you wish. I've found a related issue (mgonto/restangular#310), let me know if it works for you. |
Francois, I actually saw that Restangular issue. Unfortunately, like the creator of that ticket, I don't think that would work for my needs. I already tried to modify the path in a fullRequestInterceptor() function, but I figured I would see if there was some other possible configuration before deciding whether or not I wanted to refactor my REST API. Thank you for the quick response! |
You don't plan on adding this feature? |
If we need it for our own projects, we will. In the meantime, you're welcome to try and implement it, and submit a PR for it. |
My angular/js skill is really low, that's also why this project was really appealing until i hit this wall. |
The solution is described in #711 |
Hey guys,
I really like your project. I see from the documentation and from testing out the project that it works great for top-level entities. However, I haven't been able to figure out a way to get it working with nested entities. Is it possible to access a REST entity with a path of /firstEntity//secondEntity/?
Thanks!
The text was updated successfully, but these errors were encountered: