Hi, I was wondering if you have done any load testing profiling to know of any potential scalability issues as well as the performance characteristics?

Should reflect the following cURL example:

curl --location --request POST 'https://edge.api.flagsmith.com/api/v1/bulk-identities' \ --header 'Content-Type: application/json' \ -- header 'X-Environment-Key: <your key>' \ --data-raw '{ "data": [ {"identifier": "identity_1", "traits": [{"trait_key": "foo", "trait_value": "bar"}]}, {"identifier": "identity_2", "traits": [{"trait_key": "foo", "trait_value": "bar"}]} ] }'

gz#57

You can also optionally store and override String and numerical (int and float) values.
- https://docs.flagsmith.com/managing-features/

Traits are stored natively as either numbers, strings or booleans.
- https://docs.flagsmith.com/managing-identities/#identity-traits

I have not succesfully created a floating point value for a feature flag. Any such attempt leads to the value being coerced into a string. This experiment has not worked for traits either.

What is the actual situation regarding this?

Hi there,

It would be useful to see in the docs, why there are several different client libraries for Javascript in the frontend and for Node. Even the documented APIs seem different.

As a developer, I would want to turn the client into a single npm package, so I can re-use the same logic in my web, mobile and server side projects.
Partly, because I might change providers in the future, but also because if the client version changes and all of them have slightly different roadmaps, I end up having to change all my consumers separately if they all use a bunch of libraries directly.
So abstracting it all away into a single internal package would be the way to go.

Either way, I'm sure there are good reasons for the multitude in JS clients, would be good to document those.

Apparently there is a Slack integration: https://docs.flagsmith.com/integrations/slack

But it's missing from https://docs.flagsmith.com/integrations/overview.

gz#484

We get asked a fair bit how to delete identities via the API. Lets add these examples to the appropriate page.

To add here: https://docs.flagsmith.com/clients/rest#code-examples

Edge:
DELETE /api/v1/environments/{environment_api_key}/edge-identities/{identity_uuid}/
Core:
DELETE /api/v1/environments/{environment_api_key}/identities/{id}/

Add Google OAuth configuration to the documentation

As per logic added in this PR, we should add documentation to the kubernetes documentation here: https://docs.flagsmith.com/deployment/kubernetes.

gz#409

Full package 📦

onChange should be onChange(oldFlags: ...) and Required no/empty. i didnt realise the function passed the previous flags and had a bug, until it clicked looking at other docs needed to call getflags seperately in fn

At the moment, these environment variables are not detailed anywhere in the documentation. They are necessary to be able to configure Github OAuth when self hosting.

We should add a new section to the documentation on Authentication here: https://docs.flagsmith.com/deployment/authentication.

https://docs.flagsmith.com/deployment/locally-api#email-environment-variables

It'd be useful here to highlight that email setup is not actually needed in order to get a functional instance of flagsmith running. People are able to use invite links as a method of inviting people to an organisation.

Just to give people a high level idea of how it can work and what some simple code would look like

gz#185

One of the green "tip" messages at the top of the page says:

Some API actions require object UUIDs/IDs to be referenced. You can enable the JSON View from your account settings page which will help you access these variables.

But later down in the rest of the page, the instructions say "we're working on adding a JSON View, in the meantime you need to inspect the network requests". This is inconsistent with the green tip message and honestly, having to inspect the network requests isn't a great product experience so it's probably a good idea to get these outdated instructions removed.

gz#498