Describe the bug
When using the javascript SDK, most feature flags are never loaded. When I use chrome dev tools to inspect the request to https://app.launchdarkly.com/sdk/evalx/<key>/users/<token>, I only see 5 flags returned, despite our project having 41 flags. When calling client.variation(...) or client.variationDetail(...), it works for the ones that are returned in the request, but it does not work for all the other ones. Here is an example of what I get when I call client.variationDetail with one of the flags that are not present in the initial request:
In the console message from the console.log("ALL FLAGS: ", client.allFlags()) statement I only see the same five flags that I saw in the response from the request to https://app.launchdarkly.com/sdk/evalx/<key>/users/<token>.
Expected behavior
Would expect all flags to work.
SDK versionlaunchdarkly-js-client-sdk@2.20.2
OS/platform
Google Chrome version 98.0.4758.109 (Official Build) (x86_64)
Describe the bug When using the javascript SDK, most feature flags are never loaded. When I use chrome dev tools to inspect the request to
https://app.launchdarkly.com/sdk/evalx/<key>/users/<token>
, I only see 5 flags returned, despite our project having 41 flags. When callingclient.variation(...)
orclient.variationDetail(...)
, it works for the ones that are returned in the request, but it does not work for all the other ones. Here is an example of what I get when I callclient.variationDetail
with one of the flags that are not present in the initial request:To reproduce Here is the code I used to initialize the client:
In the console message from the
console.log("ALL FLAGS: ", client.allFlags())
statement I only see the same five flags that I saw in the response from the request tohttps://app.launchdarkly.com/sdk/evalx/<key>/users/<token>
.Expected behavior Would expect all flags to work.
SDK version
launchdarkly-js-client-sdk@2.20.2
OS/platform Google Chrome version 98.0.4758.109 (Official Build) (x86_64)