Dave Brotherstone
Dave Brotherstone
I hadn't even seen that that had been updated too, sorry. I've put it back to 1.4.4. But, what also needs to be done is to update the list in...
Wow... Looks like Don is building it himself. I'll drop him a mail, but if that's the case, then I wish he'd told me sooner - I've spent a lot...
@brightghost thanks for the clarification - we're going to address this AppData issue in #54. There are definitely some inconsistencies with how PM handles AppData and how N++ does it,...
That sounds like a really good idea to cover those cases. Should be trivial-ish to add.
Ah, I thought this was a version thing, but it doesn't look like it is - it's when you're passing an object that contains functions (functions passed directly are skipped),...
This should be pretty easy to add. This would be a great first PR :)
It should actually have a meaningful error message, there's even tests for that. I'll check it out though, you obviously managed to get weird error messages when doing this.
There are patterns to do this with unexpected-react now. You can render the component yourself (without using `when [deeply] rendered`), then render the component again as you said with new...
Thanks for the investigation and repro! I can reproduce, and am investigating the fix.
@Raigen just a question on this - what would you prefer/expect here: That the `React.Fragment` was in the assertion, or that the `React.Fragment` was flattened, as react itself does. I'm...