workflow_kit 0.0.2.alpha → 0.0.3.alpha
Sign up to get free protection for your applications and to get access to all the features.
data/Gemfile.lock
CHANGED
@@ -1,5 +1,26 @@
|
|
1
1
|
module WorkflowKit
|
2
|
-
|
3
|
-
|
2
|
+
|
3
|
+
class ApplicationController < ::ApplicationController
|
4
|
+
|
5
|
+
#
|
6
|
+
# What is this controller inheritance doing?
|
7
|
+
# This makes the class WorkflowKit::ApplicationController inherit from the main
|
8
|
+
# application's ApplicationController.
|
9
|
+
# Therefore, all helper methods of the main app will be available in the engine.
|
10
|
+
# That is necessary if you want to use the main app's layout, because this
|
11
|
+
# layout will most likely use some helper methods.
|
12
|
+
#
|
13
|
+
# To restore the isolation from the main app's ApplicationController,
|
14
|
+
# one could use the inheritance originally used by the `rails g plugin --mountable`,
|
15
|
+
# which is:
|
16
|
+
#
|
17
|
+
# class ApplicationController < ActionController::Base
|
18
|
+
#
|
19
|
+
# For further information, I recommend having a look at this extremely
|
20
|
+
# helpful article:
|
21
|
+
#
|
22
|
+
# http://bibwild.wordpress.com/2012/05/10/the-semi-isolated-rails-engine/
|
23
|
+
#
|
24
|
+
|
4
25
|
end
|
5
26
|
end
|
data/lib/workflow_kit/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: workflow_kit
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.3.alpha
|
5
5
|
prerelease: 6
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -288,7 +288,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
288
288
|
version: '0'
|
289
289
|
segments:
|
290
290
|
- 0
|
291
|
-
hash: -
|
291
|
+
hash: -378082417
|
292
292
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
293
293
|
none: false
|
294
294
|
requirements:
|