use fully qualified names for Go types
Open
enhancement
- Dominant language
- Go
- Stars
- 95
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
We're currently only using the base Go type name as the Avro name, but this can lead to name clashes if there are two types of the same name from different packages.
We could instead use a fully qualified name derived in some way (as-yet-to-be-specified) from the Go package path.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.