Ivar Conradi Østhus
Ivar Conradi Østhus
> Come to think of it, should the context be part of the timestamp "key"? Otherwise the saved toggles could be wrong if they were saved in a different context...
> The Etag seems like a good idea in absolute terms but it doesn't solve our main problem which is the number of calls to the server. Do you think...
Oh, there are a few lint issues. Do you mind running "yarn format" on it to automatically fix these @Florent-Wanteeed @jeremiewtd ?
@andreas-unleash I think it is a bug though. The SDK should still emit the `ready` after it has successfully synchronized with the Unleash API for the first time.
@AsliTuzcuogluBytro this has been released as part of version `3.4.0-beta.1`. Mind testing it and provide feedback?
Closing due to inactivity. From my standpoint using this SDK in a micro-frontend SPA is no different from any SPA, and we have multiple examples in https://github.com/Unleash/unleash-sdk-examples. The only thing...
> Related to this, is there a way to only request toggles for a specific project? It doesn't look like it. Yes, as long as you use a project specific...
I am closing this as you can achieve the same goal with scoped API tokens.
This is an oversight on our end. Your suggestion makes sense at first sight, feel free to push a PR! Thanks 👍🏼
Should the consistency level not default to ONE? http://www.datastax.com/docs/1.0/references/cql/index#specifying-consistency-level