fakefs 0.10.2 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2ad6c6a8b8e37f4902227e29ec8440158b83a888
-  data.tar.gz: 69369bfb16c12cc091e9da9d701e48aa6dd0bbb1
+  metadata.gz: 775bb49c6d9342054b77a97f0896dc5cbb1a185d
+  data.tar.gz: ecaf59b2d26c5d719a9a5ed7647eb41ddd3ebdcc
 SHA512:
-  metadata.gz: 37734960786a62c9fce7e425c5869f1f8084fd82427d0b901f7f8c2dc6c787645ba06fbb50a0c5532fcd4dd9949208c6f0c02c1c82396801d90dcbd860c7fdab
-  data.tar.gz: 53654f93f29e9b7dc76bcf7e11f4086bca6a3e997c689ef58ca5fae6771295d1514acde28073b9da3a29e2090cd096c65d9c6d83f9e45666acb73cf5ce835dd9
+  metadata.gz: 9b76df497c9c26676a079649ec241815fb972579acb5d28f884d73dfab6c9708d94807f96d252a98134a602c58b719e511b738fc0efec9eef3cfa8e9e65513c2
+  data.tar.gz: dfa04c77cbf2c5c349f9b9a90c021ea4fb5c1fffd74354c68a27e3faddff373a641117e66824806ba8cab18e3d660c2f51e16edfd4ce68fbfea8e727b9bed27b

data/README.md

@@ -96,10 +96,35 @@ end
 
 See `lib/fakefs/spec_helpers.rb` for more info.
 
-FakeFs vs `pp` --- `TypeError: superclass mismatch for class File`
+To use FakeFS within a single test and be guaranteed a fresh fake filesystem:
+``` ruby
+require 'fakefs/safe'
+
+describe "my spec" do
+  context "my context" do
+    it "does something to the filesystem"
+      FakeFS.with_fresh do
+        # whatever it does
+      end
+    end
+  end
+end
+```
+
+
+FakeFs --- `TypeError: superclass mismatch for class File`
 --------------
 
-`pp` and `fakefs` collide, `require 'pp'` then `require 'fakefs'`.
+`pp` and `fakefs` may collide, even if you're not actually explicitly using `pp`.  Adding `require 'pp'` before `require 'fakefs'` should fix the problem locally.  For a module-level fix, try adding it to the `Gemfile`:
+
+```ruby
+source "https://rubygems.org"
+
+require 'pp'
+# list of gems
+```
+
+The problem may not be limited to `pp`; any gems that add to `File` may be affected.
 
 Working with existing files
 ---------------------------
@@ -158,6 +183,9 @@ is the only thing that is guaranteed to exist, namely the root (i.e. `/`). This
 may be important when upgrading from v0.4.x to v0.5.x, especially if you depend
 on the real working directory while using FakeFS.
 
+FakeFS replaces File and FileUtils, but is not a filesystem replacement, so gems
+that use strange commands or C might circumvent it.  For example, the `sqlite3`
+gem will completely ignore any faked filesystem.
 
 Speed?
 ------

data/lib/fakefs/base.rb

@@ -21,6 +21,7 @@ module FakeFS
       @activated ? true : false
     end
 
+    # unconditionally activate
     def activate!
       Object.class_eval do
         remove_const(:Dir)
@@ -42,6 +43,7 @@ module FakeFS
       true
     end
 
+    # unconditionally deactivate
     def deactivate!
       Object.class_eval do
         remove_const(:Dir)
@@ -63,6 +65,18 @@ module FakeFS
       true
     end
 
+    # unconditionally clear the fake filesystem
+    def clear!
+      ::FakeFS::FileSystem.clear
+    end
+
+    # present a fresh new fake filesystem to the block
+    def with_fresh(&block)
+      clear!
+      with(&block)
+    end
+
+    # present the fake filesystem to the block
     def with
       if activated?
         yield
@@ -76,6 +90,7 @@ module FakeFS
       end
     end
 
+    # present a non-fake filesystem to the block
     def without
       if !activated?
         yield

data/lib/fakefs/version.rb

@@ -1,7 +1,7 @@
 module FakeFS
   # Version module
   module Version
-    VERSION = '0.10.2'.freeze
+    VERSION = '0.11.0'.freeze
 
     def self.to_s
       VERSION

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: fakefs
 version: !ruby/object:Gem::Version
-  version: 0.10.2
+  version: 0.11.0
 platform: ruby
 authors:
 - Chris Wanstrath
@@ -12,7 +12,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-01-12 00:00:00.000000000 Z
+date: 2017-04-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler