Add more documentation for 'set' method and updated error message, add client.set case using force option in order to clarify how to use this option since they are 2 positional hash arguments

Author: joecabezas

.gitignore

@@ -2,3 +2,4 @@
 .bundle
 Gemfile.lock
 coverage/
+.byebug_history

README.md

@@ -77,6 +77,16 @@ Stasche.set(user_emails: User.where(id: ids).pluck(:email))
 user_emails = Stasche.get(:user_emails)
 ```
 
+### Setting options
+The set method allows you to add an `options` hash as a second parameter, for example to set a given key even if already exists
+```rb
+# Session A
+Stasche.set({foo: 'bar'}, force: true)
+
+# Session B
+foo_value = Stasche.get(:foo)
+```
+
 ### Pushing/Peeking/Popping values
 
 ```rb

lib/stasche/store.rb

@@ -4,7 +4,7 @@ class KeyAlreadyExistsError < StandardError
 
       def initialize(key)
         super(
-          "Key #{key} already set in stasche. Use `force: true` to override."
+          "Key #{key} already set in stasche. Use `force: true` to override, example: Stasche.set({foo: 'bar'}, force: true)"
         )
       end
 

spec/stasche/client_spec.rb

@@ -74,6 +74,10 @@
         error_class = Stasche::Store::KeyAlreadyExistsError
         expect { client.set(foo: 'bar') }.to raise_error(error_class)
       end
+
+      it 'does not throws an exception if forced' do
+        expect { client.set({ foo: 'bar' }, force: true) }.to_not raise_error
+      end
     end
   end