kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/development/new_fe_guide/tips.md

36 lines
1.2 KiB
Markdown
Raw Normal View History

Add latest changes from gitlab-org/gitlab@master
2020-10-30 14:08:56 -04:00
---
stage: none
Add latest changes from gitlab-org/gitlab@master
2020-11-17 10:09:28 -05:00
group: Development
Add latest changes from gitlab-org/gitlab@master
2020-11-26 01:09:20 -05:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
Add latest changes from gitlab-org/gitlab@master
2020-10-30 14:08:56 -04:00
---
Add new frontend guide structure
2018-03-07 13:32:38 -05:00
# Tips
Add yarn clean step, to delete production compiled assets
2018-05-29 12:40:18 -04:00
## Clearing production compiled assets
To clear production compiled assets created with `yarn webpack-prod` you can run:
Add latest changes from gitlab-org/gitlab@master
2020-03-25 02:07:58 -04:00
```shell
Add yarn clean step, to delete production compiled assets
2018-05-29 12:40:18 -04:00
yarn clean
```
Adds info and links on creating feature flags Adds A short summary of the steps to create and use feature flags in development for frontend developers who might be unfamiliar with `rails` and or `flipper`. Adds links to further reading in the development guide.
2019-03-20 05:10:47 -04:00
## Creating feature flags in development
Add latest changes from gitlab-org/gitlab@master
2020-07-29 05:09:33 -04:00
The process for creating a feature flag is the same as [enabling a feature flag in development](../feature_flags/development.md#enabling-a-feature-flag-locally-in-development).
Adds info and links on creating feature flags Adds A short summary of the steps to create and use feature flags in development for frontend developers who might be unfamiliar with `rails` and or `flipper`. Adds links to further reading in the development guide.
2019-03-20 05:10:47 -04:00
Your feature flag can now be:
Reorganize feature flag documentation Split the FF docs in 3 separate docs to cover 3 different use-cases.
2019-06-27 13:52:02 -04:00
- [Made available to the frontend](../feature_flags/development.md#frontend) via the `gon`
Add latest changes from gitlab-org/gitlab@master
2020-07-29 05:09:33 -04:00
- Queried in [tests](../feature_flags/development.md#feature-flags-in-tests)
Add latest changes from gitlab-org/gitlab@master
2020-04-08 02:09:54 -04:00
- Queried in HAML templates and Ruby files via the `Feature.enabled?(:my_shiny_new_feature_flag)` method
Adds info and links on creating feature flags Adds A short summary of the steps to create and use feature flags in development for frontend developers who might be unfamiliar with `rails` and or `flipper`. Adds links to further reading in the development guide.
2019-03-20 05:10:47 -04:00
### More on feature flags
Use relative URLs in development docs This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
2019-05-19 19:27:22 -04:00
- [Deleting a feature flag](../../api/features.md#delete-a-feature)
Reorganize feature flag documentation Split the FF docs in 3 separate docs to cover 3 different use-cases.
2019-06-27 13:52:02 -04:00
- [Manage feature flags](../feature_flags/process.md)
Use relative URLs in development docs This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
2019-05-19 19:27:22 -04:00
- [Feature flags API](../../api/features.md)
Add latest changes from gitlab-org/gitlab@master
2019-12-12 19:08:05 -05:00
## Running tests locally
This can be done as outlined by the [frontend testing guide](../testing_guide/frontend_testing.md#running-frontend-tests).
Copy permalink