diff options
| author | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-20 02:27:22 +0300 |
|---|---|---|
| committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-27 18:13:40 +0300 |
| commit | 8ec7ecf0bc176c04e8f051fd4097f234037dcc79 (patch) | |
| tree | 5a993893f3c44eb0745595b276386944d66b0a5b /doc/development/ee_features.md | |
| parent | 8ae55570586ce885f84f52f88d9022736b7c1cc3 (diff) | |
Use relative URLs in development docs
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
Diffstat (limited to 'doc/development/ee_features.md')
| -rw-r--r-- | doc/development/ee_features.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/ee_features.md b/doc/development/ee_features.md index bc472bb5b0a..485d69fc997 100644 --- a/doc/development/ee_features.md +++ b/doc/development/ee_features.md @@ -933,7 +933,7 @@ export default { ``` #### For JS code that is EE only, like props, computed properties, methods, etc, we will keep the current approach - - Since we [can't async load a mixin](https://github.com/vuejs/vue-loader/issues/418#issuecomment-254032223) we will use the [`ee_else_ce`](https://docs.gitlab.com/ee/development/ee_features.html#javascript-code-in-assetsjavascripts) alias we already have for webpack. + - Since we [can't async load a mixin](https://github.com/vuejs/vue-loader/issues/418#issuecomment-254032223) we will use the [`ee_else_ce`](../development/ee_features.md#javascript-code-in-assetsjavascripts) alias we already have for webpack. - This means all the EE specific props, computed properties, methods, etc that are EE only should be in a mixin in the `ee/` folder and we need to create a CE counterpart of the mixin ##### Example: @@ -960,7 +960,7 @@ import mixin from 'ee_else_ce/path/mixin'; ### Non Vue Files For regular JS files, the approach is similar. -1. We will keep using the [`ee_else_ce`](https://docs.gitlab.com/ee/development/ee_features.html#javascript-code-in-assetsjavascripts) helper, this means that EE only code should be inside the `ee/` folder. +1. We will keep using the [`ee_else_ce`](../development/ee_features.md#javascript-code-in-assetsjavascripts) helper, this means that EE only code should be inside the `ee/` folder. 1. An EE file should be created with the EE only code, and it should extend the CE counterpart. 1. For code inside functions that can't be extended, the code should be moved into a new file and we should use `ee_else_ce` helper: |