Feature-request: Allow to define id per collection

[thomaspsik]

The "routes" feature is only implemented for "GET".

The code that needs to be changed is in server/router/plurals.js line 285 and following.

The "--id" feature is implemented through lodash_id, which allows only to change the property for all collections.

What is needed is a feature that allows to map the "id" of the collection to an arbitrary property.

Like "idmapping.json"

{ "collection_name" : "id_property_name", ... }

The functionality needs to be implemented in destroy and update.

a line like this:
db._.id = getIdForCollection(name);

getIdForCollection() must be implemented with a fallback to argv.id;

Thank you for considering.

[thomaspsik]

Alternative you could use req.query.id as an option to provide the "id property" for that call?

[brian-scb]

Yesterday I submitted a PR for a filter to get the first value for a result set, this combined with routing works as a serviceable work around for id per collection.

1386

[thomaspsik]

Yesterday I submitted a PR for a filter to get the first value for a result set, this combined with routing works as a serviceable work around for id per collection.

1386

The issue is that with routing you can "define" an id per set, but delete and patch do not consider the routing (for obvious reasons) and so there is - at the moment - no feasible way to have an identifier property different than "id", if you would like to alter the data. For readonly purposes it works just fine.

If I find the time and motivation I could implement a PR, however I would like to know which option is more preferable?

A) Provide a mapping file "idmapping.json"
{
"example" : "ex_id",
"foobar": "fooId", ...
}

B) evaluate req.query.id for each call
DELETE /example/3?id=ex_id

which would use the "ex_id" as identfier for that operation.

A) would allow to define one id property for all collections in a compact manner
B) would allow to define the id property for each individual call - allowing to use more than one "unique" property
eg. for countries: 3 letter code, 2 letter code, telephonnumber prefix are all unique

Could also do both, but that implies an order of evaluation, which could get confusing to explain?