Commit 06a07e12 authored by Mike Greiling's avatar Mike Greiling

update EE features frontend section to point to performance.md for info on page-specific EE code

parent 6cfd38e5
...@@ -360,27 +360,15 @@ Instead place EE specs in the `ee/spec` folder. ...@@ -360,27 +360,15 @@ Instead place EE specs in the `ee/spec` folder.
## JavaScript code in `assets/javascripts/` ## JavaScript code in `assets/javascripts/`
To separate EE-specific JS-files we can also move the files into an `ee` folder. To separate EE-specific JS-files we should also move the files into an `ee` folder.
For example there can be an For example there can be an
`app/assets/javascripts/protected_branches/protected_branches_bundle.js` and an `app/assets/javascripts/protected_branches/protected_branches_bundle.js` and an
EE counterpart EE counterpart
`ee/app/assets/javascripts/protected_branches/protected_branches_bundle.js`. `ee/app/assets/javascripts/protected_branches/protected_branches_bundle.js`.
That way we can create a separate webpack bundle in `webpack.config.js`: See the frontend guide [performance section](./fe_guide/performance.md) for
information on managing page-specific javascript within EE.
```javascript
protected_branches: '~/protected_branches',
ee_protected_branches: 'ee/protected_branches/protected_branches_bundle.js',
```
With the separate bundle in place, we can decide which bundle to load inside the
view, using the `page_specific_javascript_bundle_tag` helper.
```haml
- content_for :page_specific_javascripts do
= page_specific_javascript_bundle_tag('protected_branches')
```
## SCSS code in `assets/stylesheets` ## SCSS code in `assets/stylesheets`
......
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