updateState - stateEvent$ VS state$

[jan-kacina]

Hi Bradford,
I'm experiencing a strange behavior in a sated library composed from two data sources. In case of updateof one of them, the data from second one is not up-to-date...
I have digged through your source code and the reason of this behavior is StatedLib.ts line 105, where new rawState is constructed from this.stateEvent$.value.rawState - the value does not contain up-to-date data. When I change construction to use this.state$.value instead, the data are up-to-date from both data sources...

Is usage of this.stateEvent$.value.rawState intentional and important during new rawState construction? Or can it be considered as a typo and fixed?

Thanks in advance for explanation.

Regards,
Jan

[bradfordlemley]

Hi, thanks for trying the library! I'm not sure what you mean by "composed from two data sources" here...are you using mapState? I need a little more info or some code that exhibits the problem.

In line 105 that you mentioned, we're calculating the next rawState using the previous rawState (which should be this.stateEvent$.value.rawState). I believe it is correct, but would love to get more info from you to see if I'm missing something.

Thanks!

[jan-kacina]

Thanks for quick response.
By "composed from two data sources" I mean that one data for object held in rawState are taken from two different sources, e.g. two data tables.
We are using mapState as well for composing different objects together.
I'll try to prepare simple source code for problem reproduction - current project is too heavy to explain in detail