v1.4.1

Bug fixes

This release fixes a bug in the v1.4.0 release that caused nested attribute structs decorated with json annotations to stop being marshaled as they were in previous releases.

v1.4.0

Enhancements

Structs used to represent nested attributes may now be decorated with jsonapi annotations for marshaling, just as they could for unmarshaling, which can lead to more consistent types or better type reuse by @brandonc #28

Known issue: Nested object attributes decorated with json no longer marshal as they did prior to release 1.4.0. A patch release will be created soon that maintains compatibility with json annotations.

v1.3.2

This release includes a fix for polyrelation that enables a migration path from same-named relation attributes. (#27)

v1.3.1

This release includes a fix for the NullableAttr generic type's marshaling of significant null values. (#22).

v1.3.0

This release includes a new NullableAttr generic type to allow the use of significant nulls for resource attributes during PATCH operations (#21).

v1.2.0

This release includes a number of feature enhancement:

• Include upstream improvements (google/jsonapi) (#7)
• Unmarshal Links type to 'links' annotated struct fields (#10)
• Add unmarshaling of interface attribute (#11)
• Allow attributes to be marshalled for relations (#12) Any relations with non-zero attributes and non-zero primary field will now be marshaled with those attributes included (instead of just id and type), for the purposes of nested resource creation. This is not a 1.0 compliant feature, but influenced by the same behavior in the now-pending 1.1 specification.
• Polymorphic relationships may now be encoded and decoded using a new field tag "polyrelation" (#13)

1.1.0

This release includes a number of feature enhancements.

Features:

• Add RFC3339 timestamp tag: #1
• Add handler for a map[string][]string type: #2
• Add ability to unmarshal links annotation: #4