[Feature] State metadata about xstate HOT 2 CLOSED

@mogsie Good points - I wouldn't want to aggregate them naïvely, there could be conflicts (and definitely ambiguity as to which state the data relates to).

Hmm... since the way we're defining state values hierarchically (e.g., { foo: { bar: 'one', baz: 'two' } }) is essentially an easier way of defining them by ID (e.g., 'foo.bar.one', 'foo.baz.two'), we can use those unique IDs in the returned "datamodel":

State {
  value: { foo: { bar: 'one', baz: 'two' },
  data: {
    foo: // data for foo
    'foo.bar': // data for foo.bar
    'foo.bar.one': // data for foo.bar.one
    'foo.baz': // data for foo.baz
    'foo.baz.two': // data for foo.baz.two
  }
}

It looks a little funny, but the strings are the exact IDs assigned to each of the state nodes and this would guarantee no conflicts, as well as quick data look-up time (we can always have a helper function/method for retrieving data based on state, e.g., state.getData({ foo: 'bar' })).

Thoughts on this approach?

from xstate.

How would you treat substate data? And parallel state data? Would they be aggregated, or would one be able to grab them all? For parallel states it becomes difficult, because you could easily have to conflicting values for a property, both being "valid".

from xstate.