Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
0be3a416
Commit
0be3a416
authored
Aug 04, 2017
by
Lin Jen-Shin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update EE doc about where to place the files
parent
69d6e911
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
16 deletions
+16
-16
doc/development/ee_features.md
doc/development/ee_features.md
+16
-16
No files found.
doc/development/ee_features.md
View file @
0be3a416
...
@@ -17,19 +17,19 @@ as much as possible.
...
@@ -17,19 +17,19 @@ as much as possible.
Place EE-specific controllers, finders, helpers, mailers, models, policies,
Place EE-specific controllers, finders, helpers, mailers, models, policies,
serializers/entities, services, validators and workers in the top-level
serializers/entities, services, validators and workers in the top-level
`EE`
module namespace, and in
a specific
`/ee/`
sub-folder
:
`EE`
module namespace, and in
the
`ee/`
specific sub-directory
:
-
`app/controllers/ee/foos_controller.rb`
-
`
ee/
app/controllers/ee/foos_controller.rb`
-
`app/finders/ee/foos_finder.rb`
-
`
ee/
app/finders/ee/foos_finder.rb`
-
`app/helpers/ee/foos_helper.rb`
-
`
ee/
app/helpers/ee/foos_helper.rb`
-
`app/mailers/ee/foos_mailer.rb`
-
`
ee/
app/mailers/ee/foos_mailer.rb`
-
`app/models/ee/foo.rb`
-
`
ee/
app/models/ee/foo.rb`
-
`app/policies/ee/foo_policy.rb`
-
`
ee/
app/policies/ee/foo_policy.rb`
-
`app/serializers/ee/foo_entity.rb`
-
`
ee/
app/serializers/ee/foo_entity.rb`
-
`app/serializers/ee/foo_serializer.rb`
-
`
ee/
app/serializers/ee/foo_serializer.rb`
-
`app/services/ee/foo/create_service.rb`
-
`
ee/
app/services/ee/foo/create_service.rb`
-
`app/validators/ee/foo_attr_validator.rb`
-
`
ee/
app/validators/ee/foo_attr_validator.rb`
-
`app/workers/ee/foo_worker.rb`
-
`
ee/
app/workers/ee/foo_worker.rb`
If you modify an existing part of a CE controller, model, service, worker etc.
If you modify an existing part of a CE controller, model, service, worker etc.
one simple solution is to use the
`prepend`
strategy (
[
presented below
](
#overriding-ce-methods
)
).
one simple solution is to use the
`prepend`
strategy (
[
presented below
](
#overriding-ce-methods
)
).
...
@@ -117,7 +117,7 @@ end
...
@@ -117,7 +117,7 @@ end
EE-specific models should
`extend EE::Model`
.
EE-specific models should
`extend EE::Model`
.
For example, if EE has a specific
`Tanuki`
model, you would
For example, if EE has a specific
`Tanuki`
model, you would
place it in
`app/models/ee/tanuki.rb`
.
place it in
`
ee/
app/models/ee/tanuki.rb`
.
#### Code in `app/views/`
#### Code in `app/views/`
...
@@ -136,7 +136,7 @@ Place EE-specific logic in the top-level `EE` module namespace. Namespace the
...
@@ -136,7 +136,7 @@ Place EE-specific logic in the top-level `EE` module namespace. Namespace the
class beneath the
`EE`
module just as you would normally.
class beneath the
`EE`
module just as you would normally.
For example, if CE has LDAP classes in
`lib/gitlab/ldap/`
then you would place
For example, if CE has LDAP classes in
`lib/gitlab/ldap/`
then you would place
EE-specific LDAP classes in
`lib/ee/gitlab/ldap`
.
EE-specific LDAP classes in
`
ee/
lib/ee/gitlab/ldap`
.
### Classes vs. Module Mixins
### Classes vs. Module Mixins
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment