eitil 1.1.0 → 1.1.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:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 2b08b15e6b8d62cb06ba02b964c2996d06a2ab6a0384a3a6767d11aab994284b
|
4
|
+
data.tar.gz: e8bc13ea50e38201fae4272419b04f82c79ad6f2a4e7179055cc88bfcdff006a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: ff6a6f68bb479e8aa3c0e3ef71aedb34261da883913ca822d199527a605bd5bf0b94d62dff061ac5cfeea62e8e7f5cb9f39244813cdc9ba4af0bdf7b804ee1b4
|
7
|
+
data.tar.gz: 11763dbe1d14866880c06827601a0f4bf0c7bcc7fa460e0d76a7ee40b9819ad04afe7bf0a7c0cce1cbd7fc90a638ec3b4c1d46e301c8a75eb847b0e5157beddb
|
@@ -22,15 +22,21 @@ module EitilIntegrate::RubyXL
|
|
22
22
|
end
|
23
23
|
|
24
24
|
def exporter_infos
|
25
|
-
exporter_constants.map { |_c| { "#{_c}": _c.info || {} } }.inject &:merge
|
25
|
+
exporter_constants.map { |_c| { "#{_c.to_s.remove("Exporter")}": _c.info || {} } }.inject &:merge
|
26
26
|
end
|
27
27
|
|
28
|
-
alias_method :taxonomy, :exporter_infos
|
29
|
-
|
30
28
|
def exporter_info(exporter, info)
|
31
29
|
exporter_infos[exporter]&.dig(info)
|
32
30
|
end
|
33
31
|
|
32
|
+
# returns the exporter_infos, without the datatypes – for taxonomy purpuses, the field
|
33
|
+
# names are often sufficient
|
34
|
+
def exporter_taxonomy
|
35
|
+
exporter_infos.transform_values do |settings|
|
36
|
+
settings.transform_values { |info| info.first.is_a?(Hash) ? info.first.keys : info }
|
37
|
+
end
|
38
|
+
end
|
39
|
+
|
34
40
|
def exporter_params
|
35
41
|
exporter_infos.transform_values { |v| [v[:required], v[:optional]].flatten.compact }
|
36
42
|
end
|
data/eitil_wrapper/README.md
CHANGED
@@ -190,7 +190,15 @@ require "eitil_wrapper/request_logger"
|
|
190
190
|
|
191
191
|
```
|
192
192
|
|
193
|
-
The RequestLogger wrapper logs request params in /log/request_logger.log, which offers the opportunity to pry into webhooks while developing. In order to track a controller, simply
|
193
|
+
The RequestLogger wrapper logs request params in /log/request_logger.log, which offers the opportunity to pry into webhooks while developing. In order to track a controller, simply add the following. This calls a background job which writes to the file.
|
194
|
+
|
195
|
+
```ruby
|
196
|
+
|
197
|
+
include EitilWrapper::RequestLogger::ControllerMixin
|
198
|
+
before_action :log_request
|
199
|
+
|
200
|
+
```
|
201
|
+
|
194
202
|
|
195
203
|
|
196
204
|
|
data/lib/eitil/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: eitil
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.1.
|
4
|
+
version: 1.1.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Jurriaan Schrofer
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2021-06-
|
11
|
+
date: 2021-06-22 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rails
|