Commit 1d6b8eab authored by Ezekiel Kigbo's avatar Ezekiel Kigbo

Fix example block for mixin from ee-else-ce path

parent afbc8274
...@@ -909,14 +909,15 @@ export default { ...@@ -909,14 +909,15 @@ export default {
- 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`](https://docs.gitlab.com/ee/development/ee_features.html#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 - 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: ##### Example:
```javascript ```javascript
import mixin from 'ee_else_ce/path/mixin'; import mixin from 'ee_else_ce/path/mixin';
{ {
mixins: [mixin] mixins: [mixin]
} }
``` ```
- Computed Properties/methods and getters only used in the child import still need a counterpart in CE - Computed Properties/methods and getters only used in the child import still need a counterpart in CE
- For store modules, we will need a CE counterpart too. - For store modules, we will need a CE counterpart too.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment