Age | Commit message (Collapse) | Author |
|
|
|
Split the FF docs in 3 separate docs to cover 3 different use-cases.
|
|
closes 62127
|
|
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/61945
|
|
In order for there to be a single source of truth.
|
|
|
|
For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.
|
|
|
|
|
|
|
|
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 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.
|
|
This allows you to default a feature flag to 'on' when
checking whether it's enabled/disabled.
|
|
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.
|
|
|
|
|
|
The implementation now simply rely on the
`performance_bar_allowed_group_id` Application Setting.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|