#207 introduced a change where fields name in a schema can change resulting in field access by name breaking. The detailed issue [with potential solutions] is described here by @rdblue
One potential solution is to figure out how to pass a slightly different schema when building the resolving decoder
#207 introduced a change where fields name in a schema can change resulting in field access by name breaking. The detailed issue [with potential solutions] is described here by @rdblue
One potential solution is to figure out how to pass a slightly different schema when building the resolving decoder