🎚Flip or flop features in your React application in real-time backed by flag provider of your choice 🚦
Updated dependencies [612461e, 72f308b]:
#1888 72f308b Thanks @tdeekens! - The release adds a new cacheMode property on the adapterArgs of an adapter.
Using the cacheMode you can opt into an eager or lazy. The cacheMode allows you to define when remote flags should take affect in an application. Before flopflip behaved always eager. This remains the case when passing eager or null as the cacheMode. In lazy mode flopflip will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render or reconfigure.
In short, the cacheMode can be eager to indicate that remote values should have effect immediately. The value can also be lazy to indicate that values should be updated in the cache but only be applied once the adapter is configured again
With the cacheMode we removed some likely unused functionality which explored similar ideas before:
unsubscribeFromCachedFlags: This is now always the case. You can use the lazy 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 longer612461e, 72f308b]:
612461e, 72f308b]:
612461e, 72f308b]:
#1888 72f308b Thanks @tdeekens! - The release adds a new cacheMode property on the adapterArgs of an adapter.
Using the cacheMode you can opt into an eager or lazy. The cacheMode allows you to define when remote flags should take affect in an application. Before flopflip behaved always eager. This remains the case when passing eager or null as the cacheMode. In lazy mode flopflip will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render or reconfigure.
In short, the cacheMode can be eager to indicate that remote values should have effect immediately. The value can also be lazy to indicate that values should be updated in the cache but only be applied once the adapter is configured again
With the cacheMode we removed some likely unused functionality which explored similar ideas before:
unsubscribeFromCachedFlags: This is now always the case. You can use the lazy 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 longer612461e, 72f308b]:
#1888 72f308b Thanks @tdeekens! - The release adds a new cacheMode property on the adapterArgs of an adapter.
Using the cacheMode you can opt into an eager or lazy. The cacheMode allows you to define when remote flags should take affect in an application. Before flopflip behaved always eager. This remains the case when passing eager or null as the cacheMode. In lazy mode flopflip will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render or reconfigure.
In short, the cacheMode can be eager to indicate that remote values should have effect immediately. The value can also be lazy to indicate that values should be updated in the cache but only be applied once the adapter is configured again
With the cacheMode we removed some likely unused functionality which explored similar ideas before:
unsubscribeFromCachedFlags: This is now always the case. You can use the lazy 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 longer612461e, 72f308b]:
#1888 72f308b Thanks @tdeekens! - The release adds a new cacheMode property on the adapterArgs of an adapter.
Using the cacheMode you can opt into an eager or lazy. The cacheMode allows you to define when remote flags should take affect in an application. Before flopflip behaved always eager. This remains the case when passing eager or null as the cacheMode. In lazy mode flopflip will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render or reconfigure.
In short, the cacheMode can be eager to indicate that remote values should have effect immediately. The value can also be lazy to indicate that values should be updated in the cache but only be applied once the adapter is configured again
With the cacheMode we removed some likely unused functionality which explored similar ideas before:
unsubscribeFromCachedFlags: This is now always the case. You can use the lazy 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 longer612461e, 72f308b]:
612461e, 72f308b]:
612461e, 72f308b]:
612461e, 72f308b]:
#1888 72f308b Thanks @tdeekens! - The release adds a new cacheMode property on the adapterArgs of an adapter.
Using the cacheMode you can opt into an eager or lazy. The cacheMode allows you to define when remote flags should take affect in an application. Before flopflip behaved always eager. This remains the case when passing eager or null as the cacheMode. In lazy mode flopflip will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render or reconfigure.
In short, the cacheMode can be eager to indicate that remote values should have effect immediately. The value can also be lazy to indicate that values should be updated in the cache but only be applied once the adapter is configured again
With the cacheMode we removed some likely unused functionality which explored similar ideas before:
unsubscribeFromCachedFlags: This is now always the case. You can use the lazy 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 longerUpdated dependencies [612461e, 72f308b]:
Updated dependencies [612461e, 72f308b]:
Updated dependencies [612461e, 72f308b]:
612461e, 72f308b]:
612461e, 72f308b]:
#1888 72f308b Thanks @tdeekens! - The release adds a new cacheMode property on the adapterArgs of an adapter.
Using the cacheMode you can opt into an eager or lazy. The cacheMode allows you to define when remote flags should take affect in an application. Before flopflip behaved always eager. This remains the case when passing eager or null as the cacheMode. In lazy mode flopflip will not directly flush remote values and only silently put them in the cache. They would then take effect on the next render or reconfigure.
In short, the cacheMode can be eager to indicate that remote values should have effect immediately. The value can also be lazy to indicate that values should be updated in the cache but only be applied once the adapter is configured again
With the cacheMode we removed some likely unused functionality which explored similar ideas before:
unsubscribeFromCachedFlags: This is now always the case. You can use the lazy 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 longer7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
7624ccb]:
#1886 5c604ed Thanks @tdeekens! - Fix to flush flags once loaded
Updated dependencies []:
#1884 1b89d9a Thanks @tdeekens! - Fix http-adapter to reload flags right away
Updated dependencies []:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
9d6e379]:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
9d6e379]:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
Updated dependencies [9d6e379]:
9d6e379]:
Updated dependencies [9d6e379]:
#1875 6672683 Thanks @tdeekens! - Fix reversing adapter identifiers in place
Updated dependencies []:
#1875 6672683 Thanks @tdeekens! - Fix reversing adapter identifiers in place
Updated dependencies []:
#1875 6672683 Thanks @tdeekens! - Fix reversing adapter identifiers in place
Updated dependencies [6672683]:
#1875 6672683 Thanks @tdeekens! - Fix reversing adapter identifiers in place
Updated dependencies [6672683]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
#1873 e817bcc Thanks @tdeekens! - Allow cached flags to be updated silently only taking effect whenever adapter is configured again.
You can pass unsubscribeFromCachedFlags as an adapterArg to the LaunchDarkly adapter to try this out.
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
e817bcc]:
#1871 c01142b Thanks @tdeekens! - fix: path to reference for flag values
Updated dependencies []:
Updated dependencies []:
#1866 7173478 Thanks @tdeekens! - fix: restoring cached flags
Updated dependencies []: