onChange handler returns updated values in oldFlags object about flagsmith-js-client

[kyle-ssg]

Hey @harenlewis, going to schedule some time Friday to sort this. I’m sure it’ll be quite obvious when I look at it.

Ofcourse if you want to look at doing a pr in the meantime that would be amazing!

[harenlewis]

Hi @kyle-ssg any updates or workaround for this issue, I'm planning to use it for my react frontend application and discard unnecessary render caused by the onChange trigger.

Let me know if I can help in any way, would not mind working on it and submitting a PR.

[harenlewis]

@kyle-ssg Hey thanks for the reply. Sure I've gone through the code, can you help me setup the development env, I mean how to get the library running for development.
Or if there's any doc that I can refer to?

[kyle-ssg]

@harenlewis sorry for the delay, a few things.

I've deployed version 0.2.0 on bullet-train-js-client and react-native-bullet-train to resolve this issue.

• I've added instructions on developing the client library locally.
• You're correct the associated PR did break this, however old flags needed to be immutable. The above code snippet will now work.
• params now contains a flagsChanged and traitsChanged boolean which is based on a deep equals of before and after.

If you have any questions or comments just let me know and I'll reopen this!

[harenlewis]

@kyle-ssg Thanks for resolving this. I've tested it out and it works perfectly!