Ben Asher
Ben Asher
No problem. Thank you!
Ah nice! Seems like we can close this out then, since it's fixed in v7?
Ah okay. How do you get the resulting error in jest? I've been digging around, but I haven't figured out where in Jest I can add hooks to be able...
We'd also want to have it be serialized differently depending on the input/ouput format. I think implementing this right now in kotlinx.serialization is kind of kludgy. I think improvements to...
Yep string is preferred to avoid byte ordering issues across platforms
Even though kotlinx.serialization went 1.0.0 today. `@Serializer(forClass…` is still considered experimental API. For that reason, I think breaking it out into its own module makes sense. Offhand, I'm not sure...
Once an investigation is done, I have some follow up questions: 1. Are there other flags we could enable that would workaround this without giving up noImplicitAny? 2. Would pushing...
With 4.9 beta coming along, I was wondering if TypeScript folks had a chance to look at this one yet? Thanks!
@andrewbranch do you know what it is about noImplictAny that triggers this? I'm having trouble convincing the library maintainer that this is on them to fix (adding types entry under...
It would also be helpful to know if there's a way to reproduce this with prosemirror alone. Going through tiptap I think is also adding to the edge-case-y feel to...