Skip to content

Releases: tdeekens/flopflip

v13.1.3

01 Sep 13:00
9f83cb4

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

v13.1.2

21 Aug 11:25
d7c2e3e

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

v13.1.1

20 Aug 20:52
16ee5f1

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

v13.1.0

20 Aug 20:22
7f20bd7

Choose a tag to compare

@flopflip/[email protected]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #1797 34c4b6fd Thanks @tdeekens! - The useAdapterStatus hooks now allow to fetch status of one or more adapters instead of always all.

    You can pass the adapterIdentifiers argument which is of type TAdapterIdentifiers[]. This means you can:

    const status = useAdapterStatus({ adapterIdentifiers: ['http', 'memory] });

    This returns isConfigured once both adapters have reached the configurd state.

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #1797 34c4b6fd Thanks @tdeekens! - The useAdapterStatus hooks now allow to fetch status of one or more adapters instead of always all.

    You can pass the adapterIdentifiers argument which is of type TAdapterIdentifiers[]. This means you can:

    const status = useAdapterStatus({ adapterIdentifiers: ['http', 'memory] });

    This returns isConfigured once both adapters have reached the configurd state.

Patch Changes

@flopflip/[email protected]

Minor Changes

  • #1797 34c4b6fd Thanks @tdeekens! - The useAdapterStatus hooks now allow to fetch status of one or more adapters instead of always all.

    You can pass the adapterIdentifiers argument which is of type TAdapterIdentifiers[]. This means you can:

    const status = useAdapterStatus({ adapterIdentifiers: ['http', 'memory] });

    This returns isConfigured once both adapters have reached the configurd state.

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

v13.0.4

20 Aug 19:31
1dbf00f

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

v13.0.3

20 Aug 17:52
4c38dcd

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

Read more

v13.0.2

04 May 09:01
f5e52d2

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

v13.0.1

15 Mar 13:42
cd7cea2

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

v13.0.0

14 Mar 13:09
45b7cc1

Choose a tag to compare

@flopflip/[email protected]

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]

Major Changes

  • #1742 3fc3012a Thanks @userContext,! - Refactor to support v3 of the LaunchDarkly JavaScript SDK. The offical migration guide can be found here.

    If you're using LaunchDarkly as your adapter, then the shape of the adapterArgs passed to ConfigureFlopflip has changed.

    Assuming you are currently only using a user context (please refer to LaunchDarkly's documentation for more) then your previous configuration was:

    <ConfigureFlopFlip
      adapter={adapter}
      adapterArgs={{ sdk: { clientSideId }, user }}
    >
      <App />
    </ConfigureFlopFlip>

    You will have to replace user with context

    <ConfigureFlopFlip
      adapter={adapter}
    -  adapterArgs={{ sdk: { clientSideId }, user }}
    +  adapterArgs={{ sdk: { clientSideId }, context }}
    >
      <App />
    </ConfigureFlopFlip>;

    The context itself which previously was a user of for instance

    const user = {
      key: user?.id,
      custom: {
         foo: 'bar'
      }
    },

    should now be

    const context = {
      kind: 'user',
      key: user?.id,
      foo: 'bar'
    },

    Please note that if you previously used a large user object with a lot of different information you might want to think about splitting it. This is the main purpose of the change on LaunchDarkly's side.

    const deviceContext = {
      kind: 'device',
      type: 'iPad',
      key: 'device-key-123abc',
    };
    
    const userContext = {
      kind: 'user',
      key: 'user-key-123abc',
      name: 'Sandy',
      role: 'doctor',
    };
    
    const multiContext = {
      kind: 'multi',
    
      device: deviceContext,
    };

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Major Changes

  • #1742 3fc3012a Thanks @userContext,! - Refactor to support v3 of the LaunchDarkly JavaScript SDK. The offical migration guide can be found here.

    If you're using LaunchDarkly as your adapter, then the shape of the adapterArgs passed to ConfigureFlopflip has changed.

    Assuming you are currently only using a user context (please refer to LaunchDarkly's documentation for more) then your previous configuration was:

    <ConfigureFlopFlip
      adapter={adapter}
      adapterArgs={{ sdk: { clientSideId }, user }}
    >
      <App />
    </ConfigureFlopFlip>

    You will have to replace user with context

    <ConfigureFlopFlip
      adapter={adapter}
    -  adapterArgs={{ sdk: { clientSideId }, user }}
    +  adapterArgs={{ sdk: { clientSideId }, context }}
    >
      <App />
    </ConfigureFlopFlip>;

    The context itself which previously was a user of for instance

    const user = {
      key: user?.id,
      custom: {
         foo: 'bar'
      }
    },

    should now be

    const context = {
      kind: 'user',
      key: user?.id,
      foo: 'bar'
    },

    Please note that if you previously used a large user object with a lot of different information you might want to think about splitting it. This is the main purpose of the change on ...

Read more

v12.5.6

20 Feb 08:31
354f6ba

Choose a tag to compare

@flopflip/[email protected]

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]

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]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

@flopflip/[email protected]

Patch Changes

Read more