Adam Berger

This also fails for me but just incorrectly resolves the reference instead of failing with a circular ref pointer error. I believe that my issue is due to this check...

At the moment, I would like to use them [here](https://github.com/simplystated/xstate-to-gherkin) to generate gherkin tests from an xstate statechart. Meta keys are generally useful for any type of statechart reflection like...

Totally makes sense. Let me know if I can be helpful in analyzing that. If it helps, the previous behavior was to capture `meta.description` but to ignore any other field...

@Andarist - 2 thoughts: 1. I can make StateMeta in packages/machine-extractor/src/meta.ts a proxy that throws on any access to .description and run any tests or anything you had in mind...

Definitely a react-nanny bug. In https://github.com/TheSpicyMeatball/react-nanny/blob/fc64a4513397e6600ecdc7c0362587fb473781e4/src/getChildren/index.ts#L43 should be: ``` if (Array.isArray(child)) { // this is the new case to handle output = [...output, ...getChildrenDeep(child, predicate)]; } if ((child as NannyNode).props?.children)...

Thanks so much for the amazing yjs @dmonad! And thanks for putting this together @DAlperin. I'm happy to help with anything needed to get this landed if this is a...

@nathanhammond - thanks for getting back to me and totally understood and no qualms about the prioritization - it's easy to work around. However, my understanding is that `globalDependencies` actually...

The issue here is that liftListItem attempts to create a block with blockContent followed by two blockGroups. I am experimenting with changing the block schema to allow "blockContent blockGroup*" instead...