UUID route path constraint allows comma-separated ids.

[jpickwell]

Why does the constraint allow comma-separated UUIDs? I tried this with the show action, but got a { "title": "Invalid field value", "detail": "02b2dd45-c7a5-4632-8523-2ab3a68411ae,5fe60d71-9f9f-40ff-8f29-266403cb0b6f is not a valid value for id.", ... }.

This feature would be nice, and the spec does not mention URL design except as a recommendation, but even that does not mention CSV for resource id.

JR Version: 0.7.0
Commit: d5675ae

[jpickwell]

According to the spec, you cannot update multiple resources in one request: "The PATCH request MUST include a single resource object as primary data." [http://jsonapi.org/format/#crud-updating]

[mupkoo]

There is an official extension to JSONAPI which allows bulk requests - http://jsonapi.org/extensions/bulk/

[jpickwell]

The bulk extension is nice. AFAIK, JR does not support this extension, yet.

The extension only covers POST, PATCH, and DELETE. GET should be fairly straight-forward to implement. My commit (027c97d) would need to be reverted should this extension ever be implemented.

[arcreative]

This is actually an issue for a single GET request as well--just requesting <type>/<UUID> returns a 400 as well. Would be nice if it didn't :-) I'll probably be moving to short IDs in the future, but for now, UUIDs are the best and most PostgreSQL-friendly option until I spend a bit more time on the problem.

[arcreative]

Nevermind, I didn't realize there was a resource_key_type option--everything else had been working find up to this point :-)