delta/gitlab/gitlab-ce.git/doc/development/feature_flags.md, branch winh-notes-service-toggleResolveNote gitlab.com: gitlab-org/gitlab-ce.git Reorganize feature flag documentation 2019-06-27T17:52:02+00:00 Marin Jankovski marin@gitlab.com 2019-06-27T17:52:02+00:00 fda3149dda982bfca0cf57f710bc4a3edd6a6031 Split the FF docs in 3 separate docs to cover 3 different use-cases. 
Split the FF docs in 3 separate docs to cover 3 different use-cases.
Add section to dev docs on accessing chatops 2019-06-07T01:00:36+00:00 Lucas Charles me@lucascharles.me 2019-06-07T01:00:36+00:00 d3ff1e07e230812af98fa1d84ba750dc540c57fc closes 62127 
closes 62127
Use relative URLs in development docs 2019-05-27T15:13:40+00:00 Achilleas Pipinellis axil@gitlab.com 2019-05-19T23:27:22+00:00 8ec7ecf0bc176c04e8f051fd4097f234037dcc79 This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945 
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
Link to testing guide for feature flag spec info 2019-05-17T18:36:52+00:00 Luke Duncalfe lduncalfe@gitlab.com 2019-05-17T18:36:52+00:00 db7dabea674d30c170ab22b43efd86a5d91ccdfc In order for there to be a single source of truth. 
In order for there to be a single source of truth.
Replace issue with a link to the feature 2019-03-01T01:08:40+00:00 Michael Kozono mkozono@gmail.com 2019-03-01T01:08:40+00:00 16cfb7df65788da9594dc2850b26cc5ba5841854 






Remove consecutive blank lines from markdown files
2019-02-18T09:36:13+00:00

Evan Read
eread@gitlab.com

2019-02-18T09:36:13+00:00

47fb1c5235236c8e28bfdc87b013419ae1d85dc8

For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.





For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.







Add section about enabling feature flag in development
2018-12-06T16:46:12+00:00

Clement Ho
clemmakesapps@gmail.com

2018-12-06T16:46:12+00:00

d8e7e84d66feddb147efb46a6a829cdf6cf89282












Fix typos in docs
2018-11-16T10:05:55+00:00

George Tsiolis
tsiolis.g@gmail.com

2018-11-14T19:42:18+00:00

d2d8b935e2aee96e534543141d2f0beb449b7d79












Add instructions on how to enable a feature flag
2018-10-23T23:38:17+00:00

Filipa Lacerda
filipa@gitlab.com

2018-10-23T23:38:17+00:00

d240364398b5c74ef95b7516d3b4967755582a3a












Support pushing of feature flags to the frontend
2018-10-11T15:06:19+00:00

Yorick Peterse
yorickpeterse@gmail.com

2018-10-08T14:24:40+00:00

21940d1edf1604f192957691e99677d191380543

This adds a method to Gitlab::GonHelper called
`push_frontend_feature_flag`. This method can be used to easily expose
the state of a feature flag to Javascript code. For example, using this
method we may write the following controller code:

    before_action do
      push_frontend_feature_flag(:vim_bindings)
    end

    def index
      # ...
    end

    def edit
      # ...
    end

In Javascript we can then check the state of the flag as follows:

    if ( gon.features.vimBindings ) {
      // ...
    }

Fixes https://gitlab.com/gitlab-org/release/framework/issues/17





This adds a method to Gitlab::GonHelper called
`push_frontend_feature_flag`. This method can be used to easily expose
the state of a feature flag to Javascript code. For example, using this
method we may write the following controller code:

    before_action do
      push_frontend_feature_flag(:vim_bindings)
    end

    def index
      # ...
    end

    def edit
      # ...
    end

In Javascript we can then check the state of the flag as follows:

    if ( gon.features.vimBindings ) {
      // ...
    }

Fixes https://gitlab.com/gitlab-org/release/framework/issues/17