feature-flags
Here are 319 public repositories matching this topic...
-
Updated
Jun 25, 2020 - Ruby
Hi,
would it be possible to offer a swagger document that describes the REST API?
Having this, it would be easy to create additional clients, also for the administrative interfaces.
Thanks!
Cheers, Lutz.
Given input:
if(cond1 || (cond2 && experiments.isToggleEnabled(STALE_FLAG)) {
// do something
}
the output of PiranhaJava is
if(cond1 || (cond2)) {
// do something
}
The additional paranthesis around cond2 should be eliminated.
-
Updated
Jul 10, 2020 - Go
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
-
Updated
Jan 10, 2020 - PHP
Currently the http://jason-roberts.github.io/FeatureToggle.Docs/ documentation references a main CSS file (http://jason-roberts.github.io/css/main.css) that is returning a 404. This is causing the documentation to display without formatting.
-
Updated
Jul 8, 2020 - Ruby
-
Updated
Jun 30, 2020 - Elixir
-
Updated
Jul 10, 2020 - JavaScript
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.
-
Updated
Sep 27, 2019 - C#
Hi there,
I just noticed that the link to the Python Twisted SDK on the readme is broken. It's targeting the URL
http://docs.launchdarkly.com/docs/python-twisted-sdk-reference
Was it meant to target this one instead?
https://docs.launchdarkly.com/sdk/server-side/python
I also see a Python link above that one, so perhaps it's a duplicate.
Thanks and best,
Andrew
-
Updated
Apr 13, 2020 - PHP
-
Updated
Mar 14, 2020 - Ruby
-
Updated
May 25, 2020 - PHP
-
Updated
Jul 9, 2020 - Python
Was added serverside in Nov 2018 (Unleash/unleash@8e30b76#diff-07ea68e379e9e08cb74ddafcd1a3bf9c)
but is not supported yet by this client.
Involves passing ?namePrefix=value to /api/client/features
Should probably be set at initialize({...}) (optional)
-
Updated
Jun 22, 2020 - Python
-
Updated
May 1, 2017 - Elixir
-
Updated
Jul 8, 2020 - TypeScript
-
Updated
Jun 4, 2020 - JavaScript
-
Updated
Jun 27, 2020 - Go
-
Updated
Jun 29, 2020 - PHP
-
Updated
Jun 29, 2020 - Kotlin
-
Updated
Feb 26, 2020 - Kotlin
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
-
Updated
Jul 10, 2020 - Elixir
Improve this page
Add a description, image, and links to the feature-flags topic page so that developers can more easily learn about it.
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."

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 :