From 77d1f73ec1b06d919de5351cc21a1729a4186cfc Mon Sep 17 00:00:00 2001 From: Lin Jen-Shin Date: Mon, 26 Mar 2018 15:42:19 +0800 Subject: Clarify what rules we should follow for naming --- doc/development/ee_features.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc') 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 -- cgit v1.2.1