Skip to content

Releases: tdeekens/flopflip

v13.0.1

15 Mar 13:42
cd7cea2
Compare
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
Compare
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
Compare
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

v12.5.5

16 Jan 15:33
14117f2
Compare
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]

v12.5.4

21 Dec 16:39
5aaaaa7
Compare
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

v12.3.6

19 Oct 08:17
307c744
Compare
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

@flopflip/[email protected]

19 Oct 07:26
2019e76
Compare
Choose a tag to compare

Patch Changes

@flopflip/[email protected]

19 Oct 07:26
2019e76
Compare
Choose a tag to compare

Patch Changes

@flopflip/[email protected]

19 Oct 07:26
2019e76
Compare
Choose a tag to compare

Patch Changes

@flopflip/[email protected]

19 Oct 07:26
2019e76
Compare
Choose a tag to compare

Patch Changes