I'm getting an error when using the dev tools. Probably best to create a repro.
#Uncaught TypeError _owner is read-only
fierce ferry
Does the context need to be serializable? That might be an issue.
Yeah that's it...
How to I mount an unmount some DOM element? My idea was to store it in the context...
terse mist
What do you mean by dev tools?
terse mist
Ok that’s the inspector 🙂
terse mist
So yeah the machine config including the context need to be serializable to be sent over the network
fierce ferry
Do you know a good work around for this use case?
terse mist
Can you instead save a reference to the element like a function that executes a document.querySelector?
Assuming you don’t need the dom element itself and only need to have a reference to it.
fierce ferry
Might work...
terse mist
you can then call that function in the invocations and actions when you need the element itself.
fierce ferry
I can also use a global variable I guess.
terse mist
I can also use a global variable I guess.
I’d stay away from that. Unsure of side effects.
fierce ferry
I wish there was a way to disable sending the context over the wire.
But thank you, very helpful. Should I maybe make an issue so that at least a more helpful error message can be logged?
terse mist
Inspector could be more configurable but we’re planning to have an inspector mode in the visual editor.
Visual editor: https://stately.ai/editor
fierce ferry
Will the inspector be deprecated then?
terse mist
But thank you, very helpful. Should I maybe make an issue so that at least a mor...
Sure. In the meantime, inspector can may be more configurable. There’s also an RFC for a standard dev tools protocol so I’m not sure if working on the current inspector is worth it. But an issue is where we can discuss this further.
terse mist
Will the inspector be deprecated then?
Probably a while after the inspector mode is available on the visual editor to give enough time to migrate. It’ll for sure still be available even when deprecated.
terse mist
is popup a DOM element?
