Include codec name in reports

[osdiab]

with long codec errors (mitigated by #32 ) it's often hard to tell which codec exactly was erroring - would be nice if a codec name was in the message, if present

[osdiab]

whoops already does this but i just confused myself, closing

[osdiab]

nevermind i do think this doesn't get logged, reopening

[osdiab]

hmmm problem with this is that io-ts-reporter currently uses error.context.type.name to get the expected type - if you provide a name for a codec, then it actually will replace that expected type with the name of the codec you provided, effectively making this reporter much less useful. not sure if there's any way to get around that unfortunately :P gonna ask about the new io-ts decoders to see what the plans are around codec naming

[osdiab]

I think we should wait on this until the new version of io-ts becomes stable and this library can be adapted or forked for the new style of decoders. The draw() function in the new decoders is pretty nice, but it still handles unions pretty verbosely.

sandbox with union output, you can imagine how more nested unions would make this blow up: https://codesandbox.io/s/loving-saha-crub0?file=/src/index.ts

[gillchristian]

That's a good point. Let's wait for that. I think for now what we have is good enough.