apidae 1.3.8 → 1.3.9
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/app/models/apidae/obj.rb +1 -0
- data/config/initializers/cache.rb +1 -1
- data/lib/apidae/version.rb +1 -1
- data/test/dummy/log/development.log +168 -0
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 66681e7a228d04a5be420fea1d27f363dab5f3abd1431cfcfc9ddc00e1931bc1
|
4
|
+
data.tar.gz: 6872e5a2de4d23d368b00c7bb01639113afc5b1133952ce793a12e7f372885f8
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 45e6cf33a4d259a15576d28936fa7f8fc917cf4538d00c8bfec03b45b0bdde200c6cd6d536884030d2fa9d86a2313ec9e63b2bd190ff65ec6e395a19c6310acc
|
7
|
+
data.tar.gz: 40040d7672373c353358d5cba94c10f296eb6d810868d698ad11f0090456c3897c33b2838a8aeeac974bb4465f7420f37a5c5eca09cf91d40572ef4c589735b1
|
data/app/models/apidae/obj.rb
CHANGED
@@ -80,6 +80,7 @@ module Apidae
|
|
80
80
|
STR = 'STRUCTURE'
|
81
81
|
TER = 'TERRITOIRE'
|
82
82
|
|
83
|
+
# Todo : subtype for DEG shoud be :statutsExploitant (double check and fix in 1.2 and master)
|
83
84
|
TYPES_DATA = {
|
84
85
|
ACT => {node: :informationsActivite, subtype: :activiteType},
|
85
86
|
COS => {node: :informationsCommerceEtService, subtype: :commerceEtServiceType},
|
@@ -1 +1 @@
|
|
1
|
-
$apidae_cache = ActiveSupport::Cache::FileStore.new('cache/apidae', expires_in: 24.hours)
|
1
|
+
$apidae_cache = ActiveSupport::Cache::FileStore.new('cache/apidae', expires_in: ENV['APIDAE_CACHE_DURATION'] || 24.hours)
|
data/lib/apidae/version.rb
CHANGED
@@ -43,6 +43,174 @@ callback this way:
|
|
43
43
|
That block runs when the application boots, and every time there is a reload.
|
44
44
|
For historical reasons, it may run twice, so it has to be idempotent.
|
45
45
|
|
46
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
47
|
+
Rails autoloads and reloads.
|
48
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
49
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
50
|
+
|
51
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
52
|
+
to be an error condition in future versions of Rails.
|
53
|
+
|
54
|
+
Reloading does not reboot the application, and therefore code executed during
|
55
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
56
|
+
the expected changes won't be reflected in that stale Module object.
|
57
|
+
|
58
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
59
|
+
|
60
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
61
|
+
callback this way:
|
62
|
+
|
63
|
+
Rails.application.reloader.to_prepare do
|
64
|
+
# Autoload classes and modules needed at boot time here.
|
65
|
+
end
|
66
|
+
|
67
|
+
That block runs when the application boots, and every time there is a reload.
|
68
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
69
|
+
|
70
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
71
|
+
Rails autoloads and reloads.
|
72
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
73
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
74
|
+
|
75
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
76
|
+
to be an error condition in future versions of Rails.
|
77
|
+
|
78
|
+
Reloading does not reboot the application, and therefore code executed during
|
79
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
80
|
+
the expected changes won't be reflected in that stale Module object.
|
81
|
+
|
82
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
83
|
+
|
84
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
85
|
+
callback this way:
|
86
|
+
|
87
|
+
Rails.application.reloader.to_prepare do
|
88
|
+
# Autoload classes and modules needed at boot time here.
|
89
|
+
end
|
90
|
+
|
91
|
+
That block runs when the application boots, and every time there is a reload.
|
92
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
93
|
+
|
94
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
95
|
+
Rails autoloads and reloads.
|
96
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
97
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
98
|
+
|
99
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
100
|
+
to be an error condition in future versions of Rails.
|
101
|
+
|
102
|
+
Reloading does not reboot the application, and therefore code executed during
|
103
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
104
|
+
the expected changes won't be reflected in that stale Module object.
|
105
|
+
|
106
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
107
|
+
|
108
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
109
|
+
callback this way:
|
110
|
+
|
111
|
+
Rails.application.reloader.to_prepare do
|
112
|
+
# Autoload classes and modules needed at boot time here.
|
113
|
+
end
|
114
|
+
|
115
|
+
That block runs when the application boots, and every time there is a reload.
|
116
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
117
|
+
|
118
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
119
|
+
Rails autoloads and reloads.
|
120
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
121
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
122
|
+
|
123
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
124
|
+
to be an error condition in future versions of Rails.
|
125
|
+
|
126
|
+
Reloading does not reboot the application, and therefore code executed during
|
127
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
128
|
+
the expected changes won't be reflected in that stale Module object.
|
129
|
+
|
130
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
131
|
+
|
132
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
133
|
+
callback this way:
|
134
|
+
|
135
|
+
Rails.application.reloader.to_prepare do
|
136
|
+
# Autoload classes and modules needed at boot time here.
|
137
|
+
end
|
138
|
+
|
139
|
+
That block runs when the application boots, and every time there is a reload.
|
140
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
141
|
+
|
142
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
143
|
+
Rails autoloads and reloads.
|
144
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
145
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
146
|
+
|
147
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
148
|
+
to be an error condition in future versions of Rails.
|
149
|
+
|
150
|
+
Reloading does not reboot the application, and therefore code executed during
|
151
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
152
|
+
the expected changes won't be reflected in that stale Module object.
|
153
|
+
|
154
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
155
|
+
|
156
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
157
|
+
callback this way:
|
158
|
+
|
159
|
+
Rails.application.reloader.to_prepare do
|
160
|
+
# Autoload classes and modules needed at boot time here.
|
161
|
+
end
|
162
|
+
|
163
|
+
That block runs when the application boots, and every time there is a reload.
|
164
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
165
|
+
|
166
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
167
|
+
Rails autoloads and reloads.
|
168
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
169
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
170
|
+
|
171
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
172
|
+
to be an error condition in future versions of Rails.
|
173
|
+
|
174
|
+
Reloading does not reboot the application, and therefore code executed during
|
175
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
176
|
+
the expected changes won't be reflected in that stale Module object.
|
177
|
+
|
178
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
179
|
+
|
180
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
181
|
+
callback this way:
|
182
|
+
|
183
|
+
Rails.application.reloader.to_prepare do
|
184
|
+
# Autoload classes and modules needed at boot time here.
|
185
|
+
end
|
186
|
+
|
187
|
+
That block runs when the application boots, and every time there is a reload.
|
188
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
189
|
+
|
190
|
+
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
191
|
+
Rails autoloads and reloads.
|
192
|
+
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
193
|
+
DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
|
194
|
+
|
195
|
+
Being able to do this is deprecated. Autoloading during initialization is going
|
196
|
+
to be an error condition in future versions of Rails.
|
197
|
+
|
198
|
+
Reloading does not reboot the application, and therefore code executed during
|
199
|
+
initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
|
200
|
+
the expected changes won't be reflected in that stale Module object.
|
201
|
+
|
202
|
+
`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
|
203
|
+
|
204
|
+
In order to autoload safely at boot time, please wrap your code in a reloader
|
205
|
+
callback this way:
|
206
|
+
|
207
|
+
Rails.application.reloader.to_prepare do
|
208
|
+
# Autoload classes and modules needed at boot time here.
|
209
|
+
end
|
210
|
+
|
211
|
+
That block runs when the application boots, and every time there is a reload.
|
212
|
+
For historical reasons, it may run twice, so it has to be idempotent.
|
213
|
+
|
46
214
|
Check the "Autoloading and Reloading Constants" guide to learn more about how
|
47
215
|
Rails autoloads and reloads.
|
48
216
|
(called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: apidae
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.3.
|
4
|
+
version: 1.3.9
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Jean-Baptiste Vilain
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2022-03
|
11
|
+
date: 2022-05-03 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rails
|