You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -106,31 +106,31 @@ directory. The ``.split`` file has the following format: ::
106
106
107
107
file: (comment | split_line)+
108
108
comment : '#' string*\n
109
-
split_line : feature_flag_name ' ' treatment\n
110
-
feature_flag_name : string
109
+
split_line : feature_name ' ' treatment\n
110
+
feature_name : string
111
111
treatment : string
112
112
113
113
This is an example of a ``.split`` file: ::
114
114
115
115
# This is a comment
116
-
feature_flag_0 treatment_0
117
-
feature_flag_1 treatment_1
116
+
feature_0 treatment_0
117
+
feature_1 treatment_1
118
118
119
-
Whenever a treatment is requested for the feature flag ``feature_flag_0``, ``treatment_0`` is going to be returned. The same goes for ``feature_flag_1`` and ``treatment_1``. The following example illustrates the behaviour: ::
119
+
Whenever a treatment is requested for the feature ``feature_0``, ``treatment_0`` is going to be returned. The same goes for ``feature_1`` and ``treatment_1``. The following example illustrates the behaviour: ::
Notice that an API key is not necessary for the localhost environment, and the ``CONTROL`` is returned for non existent feature flags.
133
+
Notice that an API key is not necessary for the localhost environment, and the ``CONTROL`` is returned for non existent features.
134
134
135
135
It is possible to specify a different splits file using the ``split_definition_file_name`` argument: ::
136
136
@@ -161,7 +161,7 @@ Before you can use it, you need to install the ``splitio_client`` with support f
161
161
162
162
pip install splitio_client[redis]
163
163
164
-
The client depends on the information for feature flags and segments being updated externally. In order to do that, we provide the ``update_splits`` and ``update_segments`` scripts or even the ``splitio.bin.synchronizer`` service.
164
+
The client depends on the information for features and segments being updated externally. In order to do that, we provide the ``update_splits`` and ``update_segments`` scripts or even the ``splitio.bin.synchronizer`` service.
165
165
166
166
The scripts are configured through a JSON settings file, like the following: ::
167
167
@@ -198,7 +198,7 @@ These are the possible configuration parameters:
198
198
| redisDb | int | The db number on the Redis instance | 0 |
Let's assume that the configuration file is called ``splitio-config.json`` and that the client is installed in a virtualenv in ``/home/user/venv``. The feature flag update script can be run with: ::
201
+
Let's assume that the configuration file is called ``splitio-config.json`` and that the client is installed in a virtualenv in ``/home/user/venv``. The feature update script can be run with: ::
0 commit comments