Skip to content

v14.0.0

Choose a tag to compare

View all tags
@tdeekens tdeekens released this 11 Apr 12:44
· 195 commits to main since this release
v14.0.0
8714b53
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Major Changes

  • #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:

    1. unsubscribeFromCachedFlags: This is now always the case. You can use the lazy cacheMode to indicate that you don't want flags to take immediate effect
    2. subscribeToFlagChanges: This is now always true. You can't opt-out of the flag subscription any longer

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #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:

    1. unsubscribeFromCachedFlags: This is now always the case. You can use the lazy cacheMode to indicate that you don't want flags to take immediate effect
    2. subscribeToFlagChanges: This is now always true. You can't opt-out of the flag subscription any longer

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #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:

    1. unsubscribeFromCachedFlags: This is now always the case. You can use the lazy cacheMode to indicate that you don't want flags to take immediate effect
    2. subscribeToFlagChanges: This is now always true. You can't opt-out of the flag subscription any longer

Patch Changes

@flopflip/[email protected]

Major Changes

  • #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:

    1. unsubscribeFromCachedFlags: This is now always the case. You can use the lazy cacheMode to indicate that you don't want flags to take immediate effect
    2. subscribeToFlagChanges: This is now always true. You can't opt-out of the flag subscription any longer

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #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:

    1. unsubscribeFromCachedFlags: This is now always the case. You can use the lazy cacheMode to indicate that you don't want flags to take immediate effect
    2. subscribeToFlagChanges: This is now always true. You can't opt-out of the flag subscription any longer

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #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:

    1. unsubscribeFromCachedFlags: This is now always the case. You can use the lazy cacheMode to indicate that you don't want flags to take immediate effect
    2. subscribeToFlagChanges: This is now always true. You can't opt-out of the flag subscription any longer

Patch Changes

Assets 2
Loading