We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have a company resource whose ID field is cid which i access using
var companies = Restangular.withConfig(function(RestangularConfigurer){ RestangularConfigurer.setRestangularFields({ id: "cid" }); }).all('companies');
Structure of my rest api to access companies list is /api/companies/
/api/companies/
I retrieve the employee list using:
var employees = companies.one("mycid").getList('employees').$object;
Route to access employees is /api/companies/CID/employees.
/api/companies/CID/employees
now the ID field for employee is 'eid' . How can i set the configuration for employees resources to use 'eid' as the ID field.
Currently when is do employees[0].remove() ,it sends a request to
employees[0].remove()
/api/companies/CID/employees/CID.
Whereas the actual request must be sent to
/api/companies/CID/employees/EID
The text was updated successfully, but these errors were encountered:
@mgonto : Martin , Can you please reply
Sorry, something went wrong.
Hey,
You have several options to fix this issue.
Check #413 for all possibilities :).
Cheers!
No branches or pull requests
I have a company resource whose ID field is cid which i access using
Structure of my rest api to access companies list is
/api/companies/
I retrieve the employee list using:
Route to access employees is
/api/companies/CID/employees
.now the ID field for employee is 'eid' . How can i set the configuration for employees resources to use 'eid' as the ID field.
Currently when is do
employees[0].remove()
,it sends a request to/api/companies/CID/employees/CID.
Whereas the actual request must be sent to
The text was updated successfully, but these errors were encountered: