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
6696fa8f
Commit
6696fa8f
authored
Sep 20, 2017
by
Nick Thomas
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document another gotcha with the ::EE namespace
parent
945598aa
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
0 deletions
+6
-0
doc/development/ee_features.md
doc/development/ee_features.md
+6
-0
No files found.
doc/development/ee_features.md
View file @
6696fa8f
...
...
@@ -27,6 +27,12 @@ Merging changes from GitLab CE to EE can result in numerous conflicts.
To reduce conflicts, EE code should be separated in to the
`EE`
module
as much as possible.
When referencing constants
*outside*
of the
`EE`
namespace from within it, you
should always use absolute constants - e.g.,
`::User`
instead of
`User`
. This
will prevent
`::EE::User`
from being picked instead of
`::User`
. Follow this
rule even if the constant doesn't exist in the
`EE`
namespace at present - it
may be added in the future.
### Classes vs. Module Mixins
If the feature being developed is not present in any form in CE,
...
...
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