…nymore on > 0.16.4
…::Results::Collection#initialize Previously, objects have been instantiated with the hash coming from ES, duplicating _source on next save into the index. Also, make the thing less magical and admit that ActiveRecord is a beast very, very hard to tame. There must be a way to work around the `id` attribute being protected.
…d_missing) Previously, Slingshot::Persistence models allowed for setting any attribute, dynamically. So, given a class like this class Article include Slingshot::Model::Persistence include Slingshot::Model::Search include Slingshot::Model::Callbacks end you could write article = Article.new :title => 'Whatever' and the `title` attribute was saved, indexed, etc. This is no longer the case, due to erratic behaviour and implementation. You have to _explicitely_ define the attributes for your model, with the `property` method, like this: class Article include Slingshot::Model::Persistence include Slingshot::Model::Search include Slingshot::Model::Callbacks property :title end Then you can write: article = Article.new :title => 'Whatever' Slingshot::Searchable models should not be touched by this, since the must implement their own getters, setters, and `MyModel#attributes` methods.
…sk (trying to fix the test order, unit > integration)