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
I would expect that the bulk evaluation endpoint would return the same results as the individual evaluation endpoint.
Current Behavior
It returns the matched segment ID, but none of the variant information.
Steps to Reproduce (for bugs)
Always occurs on using bulk evaluate.
Context
We were hoping to load all flag data into our apps on launch to reduce network calls. At the moment, it looks like we'll need to make a network call per flag.
The text was updated successfully, but these errors were encountered:
Sorry, I thought that it matched a segment since it was including the segment in the response (and the one for an invalid flagKey did not), but I didn't have a state, so it didn't match the segment. After matching the segment I am indeed getting the variant back. (state = CA).
I do think if the request doesn't actually match a segment it probably shouldn't return one however. In the code it looks like it's just setting the segment to the last one evaluated. It makes more sense to me to only set it if it actually matches.
Expected Behavior
I would expect that the bulk evaluation endpoint would return the same results as the individual evaluation endpoint.
Current Behavior
It returns the matched segment ID, but none of the variant information.
Steps to Reproduce (for bugs)
Always occurs on using bulk evaluate.
Context
We were hoping to load all flag data into our apps on launch to reduce network calls. At the moment, it looks like we'll need to make a network call per flag.
The text was updated successfully, but these errors were encountered: