@flopflip/adapter-utilities@14.0.0
Patch Changes
@flopflip/cache@14.0.0
Major Changes
-
#1888
72f308b
Thanks @tdeekens! - The release adds a newcacheMode
property on theadapterArgs
of an adapter.Using the
cacheMode
you can opt into aneager
orlazy
. ThecacheMode
allows you to define when remote flags should take affect in an application. Beforeflopflip
behaved alwayseager
. This remains the case when passingeager
ornull
as thecacheMode
. Inlazy
modeflopflip
will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render orreconfigure
.In short, the
cacheMode
can beeager
to indicate that remote values should have effect immediately. The value can also belazy
to indicate that values should be updated in the cache but only be applied once the adapter is configured againWith the
cacheMode
we removed some likely unused functionality which explored similar ideas before:unsubscribeFromCachedFlags
: This is now always the case. You can use thelazy
cacheMode
to indicate that you don't want flags to take immediate effectsubscribeToFlagChanges
: This is now always true. You can't opt-out of the flag subscription any longer
Patch Changes
- Updated dependencies [
612461e
,72f308b
]:- @flopflip/types@14.0.0
- @flopflip/localstorage-cache@14.0.0
- @flopflip/sessionstorage-cache@14.0.0
@flopflip/combine-adapters@14.0.0
Patch Changes
@flopflip/cypress-plugin@14.0.0
Patch Changes
@flopflip/graphql-adapter@14.0.0
Minor Changes
-
#1888
72f308b
Thanks @tdeekens! - The release adds a newcacheMode
property on theadapterArgs
of an adapter.Using the
cacheMode
you can opt into aneager
orlazy
. ThecacheMode
allows you to define when remote flags should take affect in an application. Beforeflopflip
behaved alwayseager
. This remains the case when passingeager
ornull
as thecacheMode
. Inlazy
modeflopflip
will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render orreconfigure
.In short, the
cacheMode
can beeager
to indicate that remote values should have effect immediately. The value can also belazy
to indicate that values should be updated in the cache but only be applied once the adapter is configured againWith the
cacheMode
we removed some likely unused functionality which explored similar ideas before:unsubscribeFromCachedFlags
: This is now always the case. You can use thelazy
cacheMode
to indicate that you don't want flags to take immediate effectsubscribeToFlagChanges
: This is now always true. You can't opt-out of the flag subscription any longer
Patch Changes
- Updated dependencies [
612461e
,72f308b
]:- @flopflip/adapter-utilities@14.0.0
- @flopflip/types@14.0.0
- @flopflip/cache@14.0.0
- @flopflip/localstorage-cache@14.0.0
- @flopflip/sessionstorage-cache@14.0.0
@flopflip/http-adapter@14.0.0
Minor Changes
-
#1888
72f308b
Thanks @tdeekens! - The release adds a newcacheMode
property on theadapterArgs
of an adapter.Using the
cacheMode
you can opt into aneager
orlazy
. ThecacheMode
allows you to define when remote flags should take affect in an application. Beforeflopflip
behaved alwayseager
. This remains the case when passingeager
ornull
as thecacheMode
. Inlazy
modeflopflip
will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render orreconfigure
.In short, the
cacheMode
can beeager
to indicate that remote values should have effect immediately. The value can also belazy
to indicate that values should be updated in the cache but only be applied once the adapter is configured againWith the
cacheMode
we removed some likely unused functionality which explored similar ideas before:unsubscribeFromCachedFlags
: This is now always the case. You can use thelazy
cacheMode
to indicate that you don't want flags to take immediate effectsubscribeToFlagChanges
: This is now always true. You can't opt-out of the flag subscription any longer
Patch Changes
- Updated dependencies [
612461e
,72f308b
]:- @flopflip/adapter-utilities@14.0.0
- @flopflip/types@14.0.0
- @flopflip/cache@14.0.0
- @flopflip/localstorage-cache@14.0.0
- @flopflip/sessionstorage-cache@14.0.0
@flopflip/launchdarkly-adapter@14.0.0
Major Changes
-
#1888
72f308b
Thanks @tdeekens! - The release adds a newcacheMode
property on theadapterArgs
of an adapter.Using the
cacheMode
you can opt into aneager
orlazy
. ThecacheMode
allows you to define when remote flags should take affect in an application. Beforeflopflip
behaved alwayseager
. This remains the case when passingeager
ornull
as thecacheMode
. Inlazy
modeflopflip
will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render orreconfigure
.In short, the
cacheMode
can beeager
to indicate that remote values should have effect immediately. The value can also belazy
to indicate that values should be updated in the cache but only be applied once the adapter is configured againWith the
cacheMode
we removed some likely unused functionality which explored similar ideas before:unsubscribeFromCachedFlags
: This is now always the case. You can use thelazy
cacheMode
to indicate that you don't want flags to take immediate effectsubscribeToFlagChanges
: This is now always true. You can't opt-out of the flag subscription any longer
Patch Changes
- Updated dependencies [
612461e
,72f308b
]:- @flopflip/adapter-utilities@14.0.0
- @flopflip/types@14.0.0
- @flopflip/cache@14.0.0
- @flopflip/localstorage-cache@14.0.0
- @flopflip/sessionstorage-cache@14.0.0
@flopflip/localstorage-adapter@14.0.0
Patch Changes
- Updated dependencies [
612461e
,72f308b
]:- @flopflip/adapter-utilities@14.0.0
- @flopflip/types@14.0.0
- @flopflip/localstorage-cache@14.0.0
@flopflip/localstorage-cache@14.0.0
Patch Changes
@flopflip/memory-adapter@14.0.0
Patch Changes
@flopflip/react@14.0.0
Minor Changes
-
#1888
72f308b
Thanks @tdeekens! - The release adds a newcacheMode
property on theadapterArgs
of an adapter.Using the
cacheMode
you can opt into aneager
orlazy
. ThecacheMode
allows you to define when remote flags should take affect in an application. Beforeflopflip
behaved alwayseager
. This remains the case when passingeager
ornull
as thecacheMode
. Inlazy
modeflopflip
will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render orreconfigure
.In short, the
cacheMode
can beeager
to indicate that remote values should have effect immediately. The value can also belazy
to indicate that values should be updated in the cache but only be applied once the adapter is configured againWith the
cacheMode
we removed some likely unused functionality which explored similar ideas before:unsubscribeFromCachedFlags
: This is now always the case. You can use thelazy
cacheMode
to indicate that you don't want flags to take immediate effectsubscribeToFlagChanges
: This is now always true. You can't opt-out of the flag subscription any longer
Patch Changes
@flopflip/react-broadcast@14.0.0
Patch Changes
@flopflip/react-redux@14.0.0
Patch Changes
@flopflip/sessionstorage-cache@14.0.0
Patch Changes
@flopflip/splitio-adapter@14.0.0
Patch Changes
@flopflip/types@14.0.0
Minor Changes
-
#1888
72f308b
Thanks @tdeekens! - The release adds a newcacheMode
property on theadapterArgs
of an adapter.Using the
cacheMode
you can opt into aneager
orlazy
. ThecacheMode
allows you to define when remote flags should take affect in an application. Beforeflopflip
behaved alwayseager
. This remains the case when passingeager
ornull
as thecacheMode
. Inlazy
modeflopflip
will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render orreconfigure
.In short, the
cacheMode
can beeager
to indicate that remote values should have effect immediately. The value can also belazy
to indicate that values should be updated in the cache but only be applied once the adapter is configured againWith the
cacheMode
we removed some likely unused functionality which explored similar ideas before:unsubscribeFromCachedFlags
: This is now always the case. You can use thelazy
cacheMode
to indicate that you don't want flags to take immediate effectsubscribeToFlagChanges
: This is now always true. You can't opt-out of the flag subscription any longer