3.3.0 - Added cacheOptions

When calling flagsmith.init you can now pass cacheOptions

{
    ttl?:number, // how long to persist the cache in ms (defaults to 0 which is infinite)
    /*
    If this is true and there's cache available, it will skip hitting the API as if preventFetch was true
    Note: this is just for flagsmith.init(), Calls to identify, getFlags etc will still hit the API regardless
    */
    skipAPI?:boolean
}

Thanks to @qrush for the suggestion 🚀

3.2.0 fix <FlagsmithProvider /> initialisation

Prior to this release, flagsmith would initialise inside a useEffect within the FlagsmithProvider component, now it will initialise immediately as can be seen here. Initialising flagsmith asynchronously meant that the UI could flicker when default values are supplied, as well as being overall slower than it needs to be.

Thanks to @briangorham for spotting this 🚀 .

3.1.2 - Adjust Dynatrace integration syntax

In order to make the Dynatrace integration more simplistic, this replaces the dtrum init property with "enableDynatrace"

3.1.1 - Dynatrace realtime user monitoring integration

When providing dtrum instance to flagsmith.init, flagsmith will send session properties corresponding to flag enabled state, flag values and user traits. See here for an example.

• flag enabled state sends as a shortString as "true" or "false" with the prefix flagsmith_enabled_
  example: flagsmith_enabled_hero: "true"

• Remote config values sends as value with the prefix flagsmith_value_, this value will be a javaDouble for numeric values and a shortString for any other.
  example: flagsmith_value_font_size: 21, flagsmith_value_hero_colour: "blue"

• Remote config values sends as value with the prefix flagsmith_value_, this value will be a javaDouble for numeric values and a shortString for any other.
  example: flagsmith_trait_age: 21, flagsmith_trait_favourite_colour: "blue"

View the docs here!

3.1.0 - fix setTrait(s) prior to identify

Prior to this release, there were instances where calling setTrait or setTraits prior to identifying would attempt to hit the API. With this change, setTrait(s) will always build up an object of intended traits that will get sent as soon as the user is identified.

3.0.6 - fix flagsmith.setTraits

After migrating to the v2 SDK, the traits/bulk endpoint was deprecated, this release replaces that endpoint.

3.0.4: Remove increment / decrement functions

Merges:
#120 @matthewelwell 🥳

The Edge API will no longer allow for flagsmith. incrementTrait, this PR removes it from the SDK as well as examples.

3.0.3

Closes:
#118
#115
#111

Merges:
#116 Thank you @eschaefer 🥳
f0a6258 Thank you @markatom 🥳

3.0.0

Edge API as default!

2.1.0-beta.1 - Global Edge API

The Flagsmith Architecture is based around a server-side flag engine. This comes with a number of benefits, but it can increase latency, especially when the calls are being made from a location that is far from the EU; the location of our current API.

In order to solve this problem, we have developed a Global Edge API. Our aim for this API is to serve all SDK requests within 100 milliseconds, anywhere in the world. In order to achieve this, we are using the following AWS components.

This release will now use the Edge API by default for all JavaScript Client SDKs, for more information about our Edge API, view our documentation.