Serialising Flows
Before introducing flow serialising, is important to remind that Conan Flows are 2 dimensional data structures.
We believe that for most use cases, when you would like to access a flow you would like to serialise it.
Let's illustrate this graphically. Let's use again the authentication example:
Status | State 1 | State 2 | State 3 | State 4 | State 5 |
notAuthenticated | 💡 | | 💡 'invalid password' | | |
authenticating | | 💡 [username/TACOS] | | 💡 [username/password] | |
authenticated | | | | | 💡 credentials |
We provide you with two serialisation mechanisms, one to serialise everything, the other one to serialise a single status.
Both of them leverage Conan State to provide you the final serialised result.
authentication$F.toStateAll()
From the example above, this would be the visual equivalent of the generate ConanState.
| State 1 | State 2 | State 3 | State 4 | State 5 |
nextData | name
notAuthenticated data
'' | name
authenticating data
username/
TACOS | name
notAuthenticated data
'invalid pass..' | name
authenticating data
username/
password | name
authenticated data
credentials |