* The link was already there but I skipped over it on my first read.
This update makes the fact more prominent.
* I was testing to see if we wanted to move from AM Serializers to
fast_jsonapi but our API is not written according to the JSON:API spec
so, after converting one serializer over, I learned that this would not work for me.
* This update might save someone in my position the ~30 mins or so it
takes to bundle and write a serializer in the future. :)
If you include a default empty `data` option in your JSON API response,
many frontend frameworks will ignore your `related` link that could be
used to load relationship records, and will instead treat the
relationship as empty.
This adds a `lazy_load_data` option which will:
* stop the serializer attempting to load the data and;
* exclude the `data` key from the final response
This allows you to lazy load a JSON API relationship.
* add hash benchmarking to performance tests
* Add missing attribute in README example
* Disable GC before doing performance test
* Enable oj to AM for fair benchmark test
* add information on performance methodology
* add oss metadata
* Make an error that demonstrates [Issue
* Simple RSpec test that fails with a non-empty string but passes with a
non-empty symbol
* To run the test, rspec spec/lib/object_serializer_spec.rb
* Map includes to symbols if they are provided as strings
* Includes would fail with an ArgumentError unless they were explicitly
provided as symbols (see #97)
* This is solved by mapping the strings to symbols in the
ObjectSerializer initializer
* No real impact on performance here
* add hash benchmarking to performance tests
* Add missing attribute in README example
* Disable GC before doing performance test
* Enable oj to AM for fair benchmark test
* ability to customize rendering of attributes via a block
* fixed attribute render spec
* minimized specs to specifially test this feature
* Update README to include attribute definitions
* Fixed syntax error
* Fixed merge issues
