Mx Corey Frang
Mx Corey Frang
hrm Do we know what Enzyme does in this case? I'd take my answer from them?
Yeah, no need to deprecate, it's unreleased
In your usecase, the document fragment we use is stored in `context.fragment` this should be what you are looking for. It's undocumented, but that could change. One thing, with a...
I'm a little lost imagining what this would look like, do you think you could whip up a quick aircode example of what you mean with one or two of...
`.nodeName` should be `===` the function that generates it. `` = `{nodeName: 'div'}` `` = `{nodeName: Component}` Is this what you are seeing? or is there something different?
@peterjwest the recently released 1.1.0 version should allow you to do: ``` import undom from 'undom'; import {config as renderSpyConfig} from 'preact-render-spy'; renderSpyConfig.createFragment = () => undom().body; ``` This is...
@developit would `createElement('#fragment')` be better/worse?
@peterjwest got any feedback, how do you think we should document this?
I don't mind PR as a feature request in the future. I don't see a need to make an issue to make a PR, a PR is itself an "issue",...
So the current issue is that since we store both the "requested vnode" and the "rendered output" of the node, we have another "depth" that enzyme doesn't. We expose the...