kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Clarify what rules we should follow for naming

Browse source
This commit is contained in:
Lin Jen-Shin 2018-03-26 15:42:19 +08:00
parent 378d0c49e8
commit 77d1f73ec1
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/development/ee_features.md
View file

@ -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