solidus_bactracs 3.3.0 → 3.3.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0013aa0b04dbd61b4b6dc02af169425be44089ecb2cc19d2ec246ce81cb9ce2d
4
- data.tar.gz: d9e6e69eb3ddd8c81c68e39fc3b3eb8b5277c183a45e1d96e941778472beaf8b
3
+ metadata.gz: 1f2ad0b256952771d0f451dc24a4f3e18a42a0ebfc48947254a0473676fc9630
4
+ data.tar.gz: c74eeec842d70239114ff695479c0dabeeefc4af3eb869f7493eca2df1bc78bd
5
5
  SHA512:
6
- metadata.gz: a69d203aa13627e8719cd1501cc4d807a9ae20ed8c045e038592ee7448c675376d43517127f9640037ea069128db27be8d6878f388102d76a839f2727f1ceec0
7
- data.tar.gz: 80b5f4ad0db3b8c7e7fdc280cf36f825bc996bd8b8c49ebb7bb28d5e71fc272a1c5d1724503702773f0d7944d4cc4cadccac7f47489f6054a5ce47a8d001171c
6
+ metadata.gz: 5f0ed8d6d3fbca729db366a103ec0fc7ced78c9a9c41230d7467d0a2141292fbf398e08a8d64af8a915dbcab9569f1781a61215d196ea34d546f2fc21a25c4ae
7
+ data.tar.gz: 8a2e482a15f81d577922a87462c21f83ba885d09a0b6fdc55e567236b5245ecbed8b51cd9a53ecb144664ca3e882f8677b754bb2abd23258f38283580e4953c5
data/CHANGELOG.md CHANGED
@@ -1,5 +1,8 @@
1
1
  # Changelog
2
2
 
3
+ ## 3.3.0
4
+ Exposed a config var that holds an evaluator for the type of RMA being sent through bactracs. `config.evaluate_rma_type` . You should overwrite this with your own means of determining the RMA type for a given shipment.
5
+
3
6
  ## 3.1.2
4
7
  Fully include retry support tables and methods within the gem. Earlier in 3.1.x some migrations, etc, were expected to be handled by the host rails app.
5
8
 
data/README.md CHANGED
@@ -98,9 +98,19 @@ implementation, but the extension abstracts it all away for you.
98
98
 
99
99
  #### API integration: Configuration
100
100
 
101
- In order to enable the API integration, make sure to configure the relevant section of the
102
- configuration initializer. At the very least, the integration needs to know your API credentials
103
- and store ID, but there are additional options you can configure — just look at the initializer!
101
+ In order to enable the API integration, make sure to configure the relevant section of the configuration initializer. At the very least, the integration needs to know your API credentials and store ID, but there are additional options you can configure — just look at the initializer!
102
+
103
+ ##### RMA Type
104
+
105
+ This gem exposes a config var that holds an evaluator for the type of RMA being sent through bactracs. E.G. `1`, `2`, `W`, etc.
106
+
107
+ ```
108
+ config.evaluate_rma_type = proc do |shipment|
109
+ "W"
110
+ end
111
+ ```
112
+
113
+ You should overwrite this with your own means of determining the RMA type for a given shipment.
104
114
 
105
115
  #### API integration: Usage
106
116
 
@@ -146,7 +156,7 @@ This is a problem that is faced by all recurring jobs. The solution is two-fold:
146
156
 
147
157
  Because of the object abstractions in this gem, some find it difficult to test API responses vis the console. To ease such console work, a 'console harness' was developed that provides several affordances to exploratory development.
148
158
 
149
- Create a new harness in the console via
159
+ Create a new harness in the console via
150
160
 
151
161
  ```ruby
152
162
  h = SolidusBactracs::ConsoleHarness.new
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module SolidusBactracs
4
- VERSION = '3.3.0'
4
+ VERSION = '3.3.1'
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: solidus_bactracs
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.3.0
4
+ version: 3.3.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Zeryab Ali