郑达里
Oh, ok. This is an odd case because the JSON API spec says nothing about the `filter` query, but it seems that they rely on non-standard features. So in the...
The spec says absolutely nothing about filtering: > JSON API is agnostic about the strategies supported by a server. The filter query parameter can be used as the basis for...
What I meant was that any sort of filtering is out of the spec, and is ad hoc. For example, if I wanted to filter by aggregate sum of an...
Actually leave it open, I would like to keep track of it since it's useful for Ember Data.
Actually it is possible using fortune. It is just not part of the json api spec. Look for [`include`](http://fortune.js.org/api/#fortune-request) query options. Alternatively if you can afford making an additional request,...
oh yeah, using the filter option is the way to go here. I am just saying it isn't mandated nor specified, and I currently haven't implemented this in the json...
I'm not sure I understand the question. When you add properties on a record that aren't defined on the record, they end up serialized in `meta` on the individual resource....
~~Having some DNS issues even on HTTP without the S.~~ reverted to github pages
+1, would really like documentation.
Ah, your explanation of the routes clears things up. Just an example of how an `after` hook might be useful: setting the `Content-Type` on every response, without having to define...