v2.2.0

Adds real support for validations

Validations were partially supported before (as in they could be defined), but were never being enforced when remote records were saved. Additionally, the validation callbacks were not defined. Validations are now fully supported [#29, @brianstien]

v2.0.0.rc2

RC 2 of v2.0.0 reintroduces the idea of a Protobuf serializer, but purely to support lazily building messages with repeated fields. For example, when making a request with repeated fields, Active Remote previously wrapped single values in collections. This allowed for simpler searching when only a specific GUID was being passed.

Removing the Protobuf serializer and coercion in v2.0.0.rc1 broke this, but it has now been restored.

v2.0.0.rc1

The version of Active Remote depends on Protobuf v3.0.0+, making it a major version bump. The API hasn't really changed, with the exception of the Protobuf serializer being removed.

1.8.1

• Accept the class when raising RemoteRecordNotFound exceptions and include the class name in the message (i.e. "Tag does not exist).

1.8.0

• Associations now take a :scoped option to constrain association queries by the specified scope (e.g. :scoped => :user_guid).
• Add a singleton method for instantiating records that shouldn't be considered new.

1.7.1

• Fix issue where we were dependent on a specific field (guid) to determine if a record was new or not.

1.7.0

• The cache key can now be configured to use the updated_at timestamp or not (defaults to not using it)
• Including roots in JSON is now configurable (defaults to true as it does in Rails 3.2)
• Fix for #10: attributes are now properly coerced on read
• Fix for #11: bulk actions now work with Active Remote objects