When dealing with avro schema's that rely on fixed types within a different namepspace, the generated code for the standard avrohugger generator is missing an import for that fixed type.
A simple example, where we have a record with a fixed type within a different namespace to the outter.
When dealing with avro schema's that rely on fixed types within a different namepspace, the generated code for the
standard
avrohugger generator is missing an import for that fixed type.A simple example, where we have a record with a fixed type within a different namespace to the outter.
The generated code for the outter
HashRecord
excludes the required import for theSha256
record.Note I have not tested in much depth the behaviour for either
specific
orscavro
.