Currently, I’m working with a REST API that has the following convention for routes:
- Collection routes have an appended trailing slash (i.e.
- Single routes do NOT have an appended trailing slash (i.e.
What Ember-Data currently expects is no trailing slashes (REST Conventions) and therefore when working with them it appends the
id after inputting a trailing slash, resulting in an extra forward slash:
While I have currently extended the RESTAdapter’s buildURL method to look out for these use cases, I have been wondering if it is Ember’s responsibility to look for these checks by default.