summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLin Jen-Shin <godfat@godfat.org>2018-03-26 15:42:19 +0800
committerLin Jen-Shin <godfat@godfat.org>2018-03-26 15:42:19 +0800
commit77d1f73ec1b06d919de5351cc21a1729a4186cfc (patch)
tree1190edd57fd81b23838742540063045a6b2af841
parent378d0c49e81981a0a82ea054250bc259c81d5027 (diff)
downloadgitlab-ce-docs-extract-ee-api.tar.gz
Clarify what rules we should follow for namingdocs-extract-ee-api
-rw-r--r--doc/development/ee_features.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/development/ee_features.md b/doc/development/ee_features.md
index eefde13d21c..3b57180c73c 100644
--- a/doc/development/ee_features.md
+++ b/doc/development/ee_features.md
@@ -357,7 +357,8 @@ and for each different [Grape](https://github.com/ruby-grape/grape) feature,
we might need different strategies to extend it. To apply different strategies
easily, we would use `extend ActiveSupport::Concern` in the EE module.
-Put the EE module files following the same rule with other EE modules.
+Put the EE module files following
+[EE features based on CE features](#ee-features-based-on-ce-features).
#### EE API routes
@@ -387,7 +388,7 @@ constants.
#### EE params
-We can define `params` and utilize `use` in another `params` definition to
+We can define `params` and utilize `use` in another `params` definition to
include params defined in EE. However, we need to define the "interface" first
in CE in order for EE to override it. We don't have to do this in other places
due to `prepend`, but Grape is complex internally and we couldn't easily do