Mateusz Drulis

According to our TS interface and how craft was setup to work 'props' is not optional and should not be missing when serializing a node, and in such case i'm...

I'm not really sure this is the correct way going about this, this essentially results in any extra props getting automatically copy pasted into Craft state, which might result in...

@thiagoterleski see this [sandbox](https://codesandbox.io/s/recursing-hugle-36z4w?file=/src/App.tsx) that demonstrates where the issue comes from, its basically a safe check for nested Canvas components that don't have a valid id. Please double check that...

@PalTamasWBA please checkout sandbox above to see what is causing the issue, alternatively if you can provide a small sandbox with your setup we can try to debug. Version 0.2.0...

@PalTamasWBA i don't recall having any issues like that, but to be honest i'm most often using a basic CRA react starter for any development, so i hadn't tested it...

@nicosh We realised there are some unfortunate design choices in internal API's and craft state structures that don't scale too well in the long run, so that's when 0.2.0 was...

Actually @prevwong had released a package for v2 of craft that can integrate slate-js: https://www.npmjs.com/package/@craftjs/slate . It's still quite fresh and not everything works perfectly, but UX is somewhat decent....

@Mozzius i believe it lives in `next` branch with [experimental](https://github.com/prevwong/craft.js/tree/next/experimental) flag since it iss way too early to guarantee a stable API at this point.

I think that 'related' pattern doesn't really scale out that well when multi-select is at play, specifically when developing smart toolbox that shows only shared settings as per @ankri example....