In the case of events with nested field structures (multiple levels), add defaults to both the top-level record and the nested records. That's a duplicate work, but it's required by the way schema evolution works.
Default values are generated based on the registered event values. When tag ev: is present, consider aligning JSON encoding with the defined custom name.
Handle the case of nested record type referenced in multiple event schemas where each has its default value of the nested record type. A solution could be to force renaming the nested record type by adding a suffix at the tag or registry level.
In the case of events with nested field structures (multiple levels), add defaults to both the top-level record and the nested records. That's a duplicate work, but it's required by the way schema evolution works.
Default values are generated based on the registered event values. When tag
ev:is present, consider aligning JSON encoding with the defined custom name.Handle the case of nested record type referenced in multiple event schemas where each has its default value of the nested record type. A solution could be to force renaming the nested record type by adding a suffix at the tag or registry level.