Skip to content
#

feature-flags

Here are 319 public repositories matching this topic...

murtuzakz
murtuzakz commented Oct 12, 2015

Maybe I'm using it wrong, or its mentioned somewhere in the docs, and I have not read it properly.

But if you do this :

user = User.first
$rollout.activate_group(:chat, :all)      # You'd assume this activates feature for everyone, and it does.
$rollout.deactivate_user(:chat, user)  # I'm assuming this should only deactivate the feature for this user, everyone else should still have it acti
zhouzhuojie
zhouzhuojie commented Mar 20, 2019

As we are constantly upgrading Flagr server, the client SDKs may experience unexpected changes from the server side. The integration tests should better include these SDKs instead of just simple CURL tests.

Specifically, we want to cover

lucas-rudd
lucas-rudd commented Feb 18, 2020

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.

winsmith
winsmith commented Sep 6, 2017

The contributing guidelines should be a short markdown document in the root of the repository called CONTRIBUTING.md. It should be written in the Markdown format. In it, there should be a number of guidelines to keep in mind when contributing to ablator.

Below are the points that definitely need to be included, feel free to add more if you feel they are necessary. The contributing guidelines

Improve this page

Add a description, image, and links to the feature-flags topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the feature-flags topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.