Commit graph

18 commits

Author SHA1 Message Date
Lucas Charles
d3ff1e07e2 Add section to dev docs on accessing chatops
closes 62127
2019-06-07 01:00:36 +00:00
Achilleas Pipinellis
8ec7ecf0bc
Use relative URLs in development docs
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
2019-05-27 11:13:40 -04:00
Luke Duncalfe
db7dabea67 Link to testing guide for feature flag spec info
In order for there to be a single source of truth.
2019-05-17 18:36:52 +00:00
Michael Kozono
16cfb7df65 Replace issue with a link to the feature 2019-03-01 01:08:40 +00:00
Evan Read
47fb1c5235 Remove consecutive blank lines from markdown files
For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.
2019-02-18 09:36:13 +00:00
Clement Ho
d8e7e84d66 Add section about enabling feature flag in development 2018-12-06 16:46:12 +00:00
George Tsiolis
d2d8b935e2 Fix typos in docs 2018-11-16 12:05:55 +02:00
Filipa Lacerda
d240364398 Add instructions on how to enable a feature flag 2018-10-23 23:38:17 +00:00
Yorick Peterse
21940d1edf
Support pushing of feature flags to the frontend
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
2018-10-11 17:06:19 +02:00
Yorick Peterse
9393ff2fb6
Document the need for feature flags
This adds a development guide explaining that we are going to use
feature flags more often, why, what the benefits are, and so on.

See https://gitlab.com/gitlab-org/gitlab-ce/issues/49619 for more
information.
2018-09-18 16:52:44 +02:00
Brett Walker
3aea946e7f add 'default_enabled' to feature flags
This allows you to default a feature flag to 'on' when
checking whether it's enabled/disabled.
2018-09-05 09:19:16 -05:00
Gabriel Mazetto
61c35b6ca1 Fixed stub_feature_flag behavior for disabled? flags.
Previous code would not work with `disabled?` because that method would
send two parameters (second always `nil`) which we are not mocking.

Instead of mock yet another state, I decide to fix it where it belongs.
2018-08-22 05:41:15 +02:00
Zeger-Jan van de Weg
e113671faa Add Acceptance testing issue template 2018-08-15 19:48:05 +00:00
Job van der Voort
5e2c1778c2 clarify what kind of feature flags we support 2018-02-14 12:40:06 +00:00
Rémy Coutable
97611c88fc
Don't use Flipper for the Performance Bar
The implementation now simply rely on the
`performance_bar_allowed_group_id` Application Setting.

Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-07-07 02:34:51 +02:00
Rémy Coutable
e5a7d1da8c Improve Features API and its docs and add a Changelog item
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-07-06 11:18:26 +02:00
Rémy Coutable
c8ce1f0d5d Document the feature groups
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-07-06 11:18:25 +02:00
Alejandro Rodríguez
671284ba37 Add feature toggles through Flipper 2017-05-31 21:06:01 +00:00