contractinator 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 69be59e1842cf4087e1ee9456c6d141d9852ef0d
-  data.tar.gz: 468e293c29177cdec380a0263726eff3b8f2b8a0
+  metadata.gz: ed606aefaecfff4239703067517b0e2495037758
+  data.tar.gz: 6a64d437ec0b6b153db93a25f6c83613ce81c025
 SHA512:
-  metadata.gz: 3666016479f67cf80c348b634ce2bf35ae44c1a2a6008594d204fc260ad7dd524b685a950c970584cef5fb2d542564c5277570e5d97a2bed0ab56eeae6e3e135
-  data.tar.gz: 1dfa070f7b1799d6cf9fd24d8be034751a4d8b16f8206db4f7ac2630108a615d4cd463675b458c000b77c497fd835c77ad12ab18c84135d37f1da2170db25136
+  metadata.gz: 299543f8aa70f979522e24a6842b8c08634917bb09e21484fc57f0070316ade14214bb5bc50360ccfa22c38461577ef7d5a7f63b3f4d3f8feb8d2b06add50dda
+  data.tar.gz: 3b5dc5509088f867cace9640cbece9b3e949eeeda4f020fb24eed42637d469c8a0bfb9ffd9acb44cdf037c70d50b5feff2f553e984ebcecf1a386bd781e8ef4c

data/README.md

@@ -18,7 +18,7 @@ Or install it yourself as:
     
 Then inform RSpec that you'd like to use contractinator by adding something like the following to your spec_helper.rb
 
-```
+```ruby
 require 'contractinator'
 
 RSpec.configure do |config|
@@ -47,7 +47,7 @@ There are several ways to document a provider's behavior. The easiest is to use
 
 In the spec for a consumer, for example a rails controller, you might have
 
-```
+```ruby
 it 'assigns a new entry' do
   stipulate(Entry).must receive(:new).and_return(entry)
   get :new
@@ -58,14 +58,14 @@ end
 
 This sets the expectation that Entry.new will be called, and stubs it out to return `entry`. Now you should get a warning in your rspec output that looks like this:
 
-```
+```ruby
 unfulfilled contract 'Entry.new -> entry'
    at spec/controllers/entries_controller_spec.rb:45:in `block (3 levels) in <top (required)>'
 ```
 
 The next step is to make sure that contract is fulfilled by something. So we'll switch over to the model spec
 
-```
+```ruby
 describe '.new' do
   it { agree(Entry, :new).will be_a(Entry) }
 end
@@ -76,14 +76,14 @@ This calls new on Entry and asserts that it is_a Entry, and fulfills a contract
 ### Less straight-forward contracts
 Not every contract in an application is so easy to specify. For example, a view spec which assigns a local variable has an agreement with a controller to assign that variable. Some other matchers available:
 
-```
+```ruby
 assign_contract('entries#new', :entry, entry)
 flash_contract('entries#create', :notice, 'Great Success!') if flash_enabled
 ```
 
 In these two cases, the method both does the side effect (assigning a variable for a view spec or setting a flash message), and also creates a matching contract. There isn't a corresponding fulfillment matcher for anything else yet, so you have to fulfill them manually. I do this like so, in my controller spec:
 
-```
+```ruby
 describe 'get :new' do
   it { fulfills 'entries#new assign @entry'   }
   it do 
@@ -95,16 +95,16 @@ end
 ### Free-form contracts
 Sometimes I think of things that need a contract that I have no matchers for, and all I really want is a smart comment. I'm using this for a routing contract relationship now. In that case, you can do this:
 
-```
+```ruby
  # this is a contract that might be created
  # by a link in a view spec for example
- Contractinator::Contract.require("get / routes")
+ contract("get / routes")
 
 ```
 
 And fulfill it with
 
-```
+```ruby
 it { fulfills('get / routes') }
 ```
 

data/lib/contractinator/version.rb

@@ -1,3 +1,3 @@
 module Contractinator
-  VERSION = "0.1.3"
+  VERSION = "0.1.4"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: contractinator
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Ehren Murdick
@@ -11,7 +11,7 @@ authors:
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-02-18 00:00:00.000000000 Z
+date: 2016-02-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec