pact-message 0.11.0 → 0.11.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f26e9b2d322f3bb375df2197aa2180f8de0b4d62e45decf77e4c4b3802505ffa
-  data.tar.gz: 130523097c7c65ddc0bf9d9dbf4464d7d17dfb7de97c7ef97471535be265e382
+  metadata.gz: 8ce8daa35756cfc3bf55b364cc91d123ab92be909f37d56fa237bcdb2a4051b2
+  data.tar.gz: d404290cbd697430bc277ef2298e37f17ab8c2770b999d0824cde92f8eafd306
 SHA512:
-  metadata.gz: 184da6d526714237d5ec94c7a27b5c8e8562a91023cd6ede596e6a7aa8adf34ba1249650a01f4f50bcdcbd78fa529799cfd04922a00a51f90f832477f7cd35ff
-  data.tar.gz: 8b24b7de4e4d24c41e4520d5ba0008d3ca719f7be4c17fa7c0d70d7bf4ea0fcb32e1910fcb37b543b4040d16e02f9ac672e478dfe06f6961bdbff86a67b7378f
+  metadata.gz: 6b5a5052f06c36a369453082962d74c893ca7a235efbfae622c7fa64b3f156267db773708e3ae0d783cbe39d7d620e97f7ad70f7a728aa7d4322ab11cd148f35
+  data.tar.gz: 551b8239e8bc1374405acfcee1f4dee500df58bd4a6f63bccee2f85fe5231ba680a4df4113685e1e8c30ff4b52cca8ba210d9032399d9ad0dc2c8553e5e7eed8

data/CHANGELOG.md

@@ -1,3 +1,10 @@
+<a name="v0.11.1"></a>
+### v0.11.1 (2021-04-20)
+
+#### Bug Fixes
+
+* JSON load message document so that the Ruby objects are created properly	 ([2bab66c](/../../commit/2bab66c))
+
 <a name="v0.11.0"></a>
 ### v0.11.0 (2021-03-22)
 

data/README.md

@@ -31,6 +31,7 @@ The key to using Message Pact is to completely separate the business logic that
 ### Consumer
 
 Not finished yet as nobody has asked for it. Ping @Beth Skurrie on slack.pact.io if you'd like use this.
+Update: Done but not documented yet. See https://github.com/pact-foundation/pact-message-ruby/blob/master/spec/features/create_message_pact_spec.rb#L78 for an example.
 
 ### Provider
 

data/lib/pact/message/cli.rb

@@ -14,17 +14,17 @@ module Pact
       long_desc <<-MSG, wrapping: false
         Update a pact with the given message, or create the pact if it does not exist.
         The MESSAGE_JSON may be in the legacy Ruby JSON format or the v2+ format.
-        If MESSAGE_JSON is not provided or is '-', the content will be read from 
+        If MESSAGE_JSON is not provided or is '-', the content will be read from
         standard input.
       MSG
       def update(maybe_json = '-')
         require 'pact/message'
         require 'pact/message/consumer/write_pact'
 
-        message_json = JSON.parse(maybe_json == '-' ? $stdin.read : maybe_json)
+        message_object = JSON.load(maybe_json == '-' ? $stdin.read : maybe_json)
 
         pact_specification_version = Pact::SpecificationVersion.new(options.pact_specification_version)
-        message_hash = Pact::Message.from_hash(message_json, { pact_specification_version: pact_specification_version })
+        message_hash = Pact::Message.from_hash(message_object, { pact_specification_version: pact_specification_version })
         Pact::Message::Consumer::WritePact.call(message_hash, options.pact_dir, options.consumer, options.provider, options.pact_specification_version, :update)
       end
 
@@ -39,6 +39,12 @@ module Pact
         require 'pact/message/version.rb'
         puts Pact::Message::VERSION
       end
+
+      no_commands do
+        def self.exit_on_failure?
+          true
+        end
+      end
     end
   end
 end

data/lib/pact/message/version.rb

@@ -1,5 +1,5 @@
 module Pact
   module Message
-    VERSION = "0.11.0"
+    VERSION = "0.11.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pact-message
 version: !ruby/object:Gem::Version
-  version: 0.11.0
+  version: 0.11.1
 platform: ruby
 authors:
 - Beth Skurrie
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-03-22 00:00:00.000000000 Z
+date: 2021-04-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: pact-support
@@ -212,7 +212,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.15
+rubygems_version: 3.2.16
 signing_key: 
 specification_version: 4
 summary: Consumer contract library for messages