mm-tree 0.1.0 → 0.1.1

data/README.rdoc

@@ -11,7 +11,10 @@ Rational numbers is even better than left/right trees, as you can remove parts o
 
 == Installation
 
-I assume you are using bundler, so add this to your Gemfile:
+If you are using bundler, and want latest stable gem
+  gem 'mm-tree'
+
+For latest edge version:
   gem 'mm-tree', :git => 'http://github.com/leifcr/mm-tree.git'
 
 == Usage

data/lib/mongo_mapper/plugins/tree.rb

@@ -187,7 +187,13 @@ module MongoMapper
       def set_nv_dv_if_missing
         return if !tree_use_rational_numbers
         if (self.tree_info.nv == 0 || self.tree_info.dv == 0 )
-          new_keys = self.next_keys_available(self[tree_parent_id_field], (self.has_siblings? + 1) )
+          last_sibling = self.siblings.last
+          if (last_sibling == nil)
+            last_sibling_position = 0
+          else
+            last_sibling_position = self.class.position_from_nv_dv(last_sibling.tree_info.nv, last_sibling.tree_info.dv)
+          end
+          new_keys = self.next_keys_available(self[tree_parent_id_field], (last_sibling_position + 1) )
           self.tree_info.nv = new_keys[:nv]
           self.tree_info.dv = new_keys[:dv]
           self.tree_info.snv = new_keys[:snv]

data/lib/version.rb

@@ -1,6 +1,6 @@
 # encoding: UTF-8
 module MongoMapper
   module Tree
-    Version = '0.1.0'
+    Version = '0.1.1'
   end
 end

data/test/test_tree.rb

@@ -270,7 +270,7 @@ class TestMongomapperActsAsTree < Test::Unit::TestCase
         assert @node_2_4_1_1.ancestor_tree_keys() == @node_2_4_1.tree_keys(), "After move: #{@node_2_4_1_1.name} ancestor keys should match #{@node_2_4_1.name} got: #{@node_2_4_1_1.ancestor_tree_keys()} expected: #{@node_2_4_1.tree_keys()}"
       end
       
-      should "should have changed nv/dv after changing parent (id)" do
+      should "have changed nv/dv after changing parent (id)" do
         old_keys = @node_1_2.tree_keys()
         @node_1_2.parent = @node_2
         # before saved
@@ -286,6 +286,15 @@ class TestMongomapperActsAsTree < Test::Unit::TestCase
         # should still be able to find correct keys for child of moved item
         assert @node_1_2_1.ancestor_tree_keys() == @node_1_2.tree_keys(), "After move #{@node_1_2_1.name} ancestor keys should match #{@node_1_2.name} got: #{@node_1_2_1.ancestor_tree_keys()} expected: #{@node_1_2.tree_keys()}"
       end
+
+      should "have correct keys after destroying a sibling and creating a new item" do
+        old_id = @node_1_2._id
+        @node_1_2.destroy
+        Category.find(old_id).should == nil
+        node_1_4    = Category.create(:name => "Node 1.4", :parent => @node_1)
+        node_1_4.tree_keys.should_not == Hash[:nv => 7, :dv => 4, :snv => 9, :sdv => 5]
+        node_1_4.tree_keys.should == Hash[:nv => 9, :dv => 5, :snv => 11, :sdv => 6]
+      end
     end # tree keys
 
     should "rekey the entire treestructre" do

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mm-tree
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-20 00:00:00.000000000 Z
+date: 2012-08-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: mongo_mapper
@@ -61,12 +61,18 @@ required_ruby_version: !ruby/object:Gem::Requirement
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
+      segments:
+      - 0
+      hash: -3601179477307526079
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
+      segments:
+      - 0
+      hash: -3601179477307526079
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.24