apidragon 1.4.4 → 1.4.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 44bb4be6262015a0aa0ff2dba46b53287fc0b850
-  data.tar.gz: e0d111a9314736c705ce63c019becbd979f288ba
+  metadata.gz: ba5645d669bed63e76fa86bb835fc5f0ab27b874
+  data.tar.gz: bf3ff860f629dd508006626bee57bff1685583f2
 SHA512:
-  metadata.gz: 18ed7633a06eea950570edb21a0ee5753730d2f2608a806136730f573d0c55150ee582e568b52927aceca09061bfa1988e6d702ccfa99fb9495e1fc985f63071
-  data.tar.gz: caf38194a06121ad8129c4accf4347e9b2ea114565c689895b947037e26bc0bf1d7b449e497591d374565b1eb0a5141fbfa7ce8c735b4175dfdb5390a3264700
+  metadata.gz: fdf4c6a02cc8f8fec3e89e7345c46af29f6b1118ca8f5b1c5f4a0c5cbbd317b4c250c2aef10b6fb55787d8c1eacb356ff2c920abd9debe6b3c8266093df5ce8d
+  data.tar.gz: 26c6832181e0a17d7754d7e40559e77ccebb4a97bb8f2623db9b565de46a38289412c597b42a453de4e0308438b4edb80ed6b7b174a018c6e9fd6ba5495e9762

data/README.md

@@ -113,7 +113,9 @@ Each call can have a `record` option, where you can specify what output variable
 ```
 
 ## Qualifier variables
-Further, for more specific output parsing, you can specify a qualifier variable. As long as responses are returned as `xml` or `json`, output variables can be associated with one of your pre-defined values for cases like parsing lists of values that have several attribute fields.  
+apidragon automatically returns the first instance it finds of the specified output variable in the response.
+
+For more specific output parsing, you can specify a qualifier variable. As long as responses are returned as `xml` or `json`, output variables can be associated with one of your pre-defined values for cases like parsing lists of values that have several attribute fields.  
 
 - e.g.:
 ```yaml
@@ -125,12 +127,12 @@ Further, for more specific output parsing, you can specify a qualifier variable.
 So if the call returns a list like this: `[{username => bob, id => 1234}, {username => alice, id => 5678}]`, you can always return the `id` associated with the `username` variable defined in the `vars` section.
 
 ## logging
-For each call, set `logging` to `true` to enable or `false` to disable. (Note: must explicitly set `logging: false` if a previous call has it set to `true`. Still trying to figure out why this is)
+Loggin can be disabled by specifying `logging` to be `false`, as per below.
 
 - e.g.:
 ```yaml
   testcall:
-    logging: true
+    logging: false
 ```
 
 ## plugin

data/VERSION

@@ -1 +1 @@
-1.4.4
+1.4.5

data/bin/apidragon

@@ -6,7 +6,7 @@ require_relative '../lib/apidragon.rb'
 
 Commander.configure do
   program :name, 'apidragon'
-  program :version, '1.4.4'
+  program :version, '1.4.5'
   program :description, 'CLI for automating api requests'
   program :help, 'Author', 'Isaiah Thiessen <isaiah.thiessen@telus.com>'
 

data/lib/apidragon/macro.rb

@@ -99,10 +99,11 @@ class Call < ArgBucket
   end
 
   def xml_to_json
-    @response = JSON.parse(Hash.from_xml(@response).to_json) unless !@response.include?('<?xml')
+    @response = Hash.from_xml(@response).to_json unless !@response.include?('<?xml')
   end
 
   def parse_response
+    @response = JSON.parse @response
     @output.each do |var|
       if var.is_a? String
         parser = Parser.new(var, nil, @response)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: apidragon
 version: !ruby/object:Gem::Version
-  version: 1.4.4
+  version: 1.4.5
 platform: ruby
 authors:
 - isaiah thiessen