This, to me makes more sense for someone first using the gem. When ordered by descending position, new items are added to the top of the list which makes less sense than the traditional addition to the bottom of a list as is often the case in first in first out lists. This also makes move_higher and other methods a little easier to understand when first being introduced to the gem.
Add license info: license file and gemspec
…_to_travis Add support for JRuby and Rubinius specs
… to include these VMs. Add begin/rescue block to Rakefile for RDocTask
Use the correct syntax for conditions in Rails 4 on the readme.
…b.com:webdoc * 'master' of github.com:webdoc/acts_as_list: Add missing quote for id in sql request. Add quote for id in sql request (for when id is a uuid string for example). Conflicts: lib/acts_as_list/active_record/acts/list.rb
Squashed commits follow: Fix issue with old order not being set When moving an item between lists, previously the old order was not being set on the record before calling `decrement_positions_on_lower_items`. This had the side effect of leaving the previous list with duplicate or incorrect order numbers if you moved the item to a new list with a different position. TODO: Add support for multiple scope conditions when moving an item between lists. Refactor `check_scope` for clarity and DRYness. Conflicts: lib/acts_as_list/active_record/acts/list.rb Add failing tests Add failing tests for moving items between lists with multiple scopes Implement moving between lists with array scope When check_scope is called it checks if there have been any changes to scope properties. This is handled by a new private method, scope_changed? which looks at a new method 'scope' which returns the raw scope data. If the scope has changed, swap_changed attributes is called, this sets all the changes back to the objects previous state so we can update it's previous list. The changes are then swapped back using the same method and we add it to the new list. TODO: - Consider changing check_scope to a better name like update_previous_list? - How should this handle scopes that use string interpolation? Should the scope always be considered changed? Remove scope_name function Add comments to private methods Add tests for changing only one scope property Previous tests only covered changing all scope properties at once. Add tests for moving to empty list Add scope_name function back in Pass move_within_scope tests
Test against activerecord v3 and v4
Add tests for moving within scope and add method: move_within_scope