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
When the FE is updating the multivariate_feature_state_values (MVFSVs) associated with a given feature state, it seems
to be using the ID of the multivariate_feature_option (MVFO), not the ID of the MVFSV. I've included some sample
requests below taken from the network console.
Step 1. User creates a new feature with 3 variations of 20, 30 & 40% weightings respectively
The request for this is irrelevant.
Step 2. User closes and reopens the feature in a given environment
FE makes a GET request to /api/v1/environments/:id/featurestates/:id/ with the following response body:
When the FE is updating the
multivariate_feature_state_values
(MVFSVs) associated with a given feature state, it seemsto be using the ID of the
multivariate_feature_option
(MVFO), not the ID of the MVFSV. I've included some samplerequests below taken from the network console.
Step 1. User creates a new feature with 3 variations of 20, 30 & 40% weightings respectively
The request for this is irrelevant.
Step 2. User closes and reopens the feature in a given environment
FE makes a GET request to
/api/v1/environments/:id/featurestates/:id/
with the following response body:Note that the ids of the MVFSVs themselves are different to the ids of the MVFOs.
Step 3. User attempts to resave the feature (without changing anything)
The FE makes a PUT request to
/api/v1/environments/:id/featurestates/:id/
with the following body:Note that the ids are now that of the MVFOs not the ids that were returned for the MVFSVs.
The text was updated successfully, but these errors were encountered: