jnunemaker / flipper-ui Goto Github PK

Right now it looks like this:

I just hacked it in so I could see it working in some fashion.

We also might want to combine the groups/actors tabs and do a split column view where one column is for actors and one is for groups. Neither will take up the full space currently, so this might be handy.

/cc @orderedlist

• loading features
• saving gate values
• etc.

Some of the gates return an error and message when invalid data is used to update a value. We should detect this in the UI and show the error messages.

I would like to use the flipper with flipper ui, but it seems to not be ended. Is it possible to start the use of this gems and help you develop this? Would also be possible to just use the feature flag?

best.

Click change settings. Enable group, turn on/off, add an actor, up the percentage, etc.

If you have a feature:

flipper["feature:v1"].enable

And you try to use flipper-ui to disable it:

• Click "Change Settings"
• Select the "Off" radio button
• Click "Save Settings"

Then when you refresh the UI (re-request base flipper-ui URL) you'll see that a new feature named "feature%3av1" was created and disabled.

So, I'm assuming this is a simple case where any feature with characters that get URL-escaped by the browser when it sends a request creates a new feature since flipper-ui doesn't unescape the feature-name part of the path segment.

I love the idea of the flipper ecosystem. How is it coming?

Each gates text/help/instructions should be customizable so companies/developers can make it feel more like there own. I can also see providing an actor to instance conversion block for changing things like User:6 to @jnunemaker or whatever makes sense.

Right now if you remove a member from a set (group, actor) and the ajax fails behind the scenes, no error is shown and the dom element is removed from the list.

Instead, we should show an error in the UI and also add the failed disable back into the dom.

Currently forced to be /flipper.

Right now if you add a member to a set (group, actor) and the ajax fails behind the scenes, no error is shown and the dom elements stays in the list.

Instead, we should show an error in the UI and also remove the failed enable from the set members.

Enabled, Disabled, Enabled for this user/group/etc.

Right now if there are no features it just shows the flipper logo and a blank page. We should inform the user that there are no features right now and show them how to get started.

I have this line in my flipper.rb config file:
Flipper::UI.feature_creation_enabled = false

It no longer seems supported as I look to upgrade flipper. Can you point me to the correct way to do this?

Right now it redirects to feature list.

Now that we have Flipper::UI it would be nice to have Flipper::API. Flipper::API would provide the same functionality as the UI but all json responses instead of html/css views. Clients could then be created for chatops/hubot to enable/disable features and all that.

When ajax operations fail we should provide feedback in the UI in some way (alert or whatever).

bundle update doesnt work because the flipper-ui gem is not published on Rubygems (or at least I could not find it)

Right now if you enable/disable something for a gate and then hit cancel, the state (colored box) and description text for the feature are not updated, but should be.