Closed steve-e closed 8 months ago
thanks again for the report, @steve-e
Possible solutions: as I see it,
My own timeframe is pretty far out, currently, but happy to help with what I can:
Background: regarding avrohugger's import system,
Current Status: Slowly replacing the import system by instead generating fully qualified names (e.g., here, and here)
fixed by #191
We have come up against the following problem. If a record has 2 fixed types in different namespaces but same schema name then the code generated does not compile.
Here is an example avro schema dmonstrating the problem
Using these typical test settings
This generates 3 source files
target/generated-sources/specific/fixedtwo/FixedTwo.scala target/generated-sources/specific/fixedtwo/one/fixed.scala target/generated-sources/specific/fixedtwo/two/fixed.scala
The fixed classes are in different packages so having the same simple class name is not a problem
However, the
FixedTwo
record class imports bothfixed
classesThis causes a compilation error as the name
fixed
is ambiguous.