active_model_serializers/benchmarks/serialization_libraries
Benjamin Fleischer 68720cef4d Confirmed difference from jsonapi vs AMS not significant
pretty clear now that the ONLY difference
rendering a `user` with `include: 'posts.comments'`
is that the included post's user relationship
in jsonapirb is `meta: { included: false }`
and AMS is `data: { id: 1, type: users}`

which I guess is to avoid the user's
post's comment from looking up the user?

similarly, the included comment's post relationship
for jsonapi-rb is `meta: { included: false}`
and AMS is `data: { id: 2, type: posts }`

took a bit of jq and diff to figure this out
2017-10-13 23:16:58 -05:00
..
support Make all ids increment for uniquness and sortability 2017-10-13 22:28:08 -05:00
benchmark.rb Assert no regressions in gem-specific JSON document 2017-10-13 22:06:42 -05:00
compare.sh Confirmed difference from jsonapi vs AMS not significant 2017-10-13 23:16:58 -05:00
Gemfile compare ams with jsonapi-rb 2017-08-03 08:39:02 -04:00
Gemfile.lock Benchamrks are an app which requires us to track the Gemfile.lock 2017-10-12 15:32:42 -05:00