lspace 0.11 → 0.12

data/README.md

@@ -208,3 +208,15 @@ end
 A new `LSpace` will by default inherit everything from its parent, so it's better to store
 `LSpace.new` than `LSpace.current`, so that if the user mutates their LSpace in a
 callback, the change does not propagate upwards.
+
+Testing
+=======
+
+If you're using `LSpace`, you probably want each test case to run in its own `LSpace` so
+that tests cannot pollute each other. If you're using rspec you can do this with:
+
+```ruby
+require 'lspace/rspec'
+```
+
+If not, you'll have to add an around filter yourself.

data/lib/lspace/rspec.rb

@@ -0,0 +1,7 @@
+RSpec.configure do |c|
+  c.around(:each) do |example|
+    LSpace.clean do
+      example.run
+    end
+  end
+end

data/lspace.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name = "lspace"
-  s.version = "0.11"
+  s.version = "0.12"
   s.platform = Gem::Platform::RUBY
   s.author = "Conrad Irwin"
   s.email = "conrad.irwin@gmail.com"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: lspace
 version: !ruby/object:Gem::Version
-  version: '0.11'
+  version: '0.12'
   prerelease: 
 platform: ruby
 authors:
@@ -140,6 +140,7 @@ files:
 - lib/lspace/class_methods.rb
 - lib/lspace/core_ext.rb
 - lib/lspace/eventmachine.rb
+- lib/lspace/rspec.rb
 - lib/lspace/thread.rb
 - lspace.gemspec
 - spec/celluloid_spec.rb