This is an automated email from the ASF dual-hosted git repository.
kriskras99 pushed a change to branch feat/serde_transparent
in repository https://gitbox.apache.org/repos/asf/avro-rs.git
discard a7544e1 fix(derive): UI test updates to new error string
discard 06905ba fix(derive): Improve type handling for `serde(transparent)`
discard 6b9a15f feat(derive): Support `#[serde(transparent)]`
add 6fc1f96 fix duplicate serialization of logicalType key for logical
type schemas based on fixed type (#395)
add 578ffd9 chore(deps): Bump miniz_oxide from 0.8.9 to 0.9.0 (#399)
add 6492782 feat!:Make AvroSchemaComponent available without `derive`
feature (#394)
add 728310d feat(derive): Support `#[serde(transparent)]`
add 81e103d fix(derive): Improve type handling for `serde(transparent)`
add caeac48 fix(derive): UI test updates to new error string
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a7544e1)
\
N -- N -- N refs/heads/feat/serde_transparent (caeac48)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
Cargo.lock | 13 +-
avro/Cargo.toml | 2 +-
avro/src/codec.rs | 1 +
avro/src/lib.rs | 4 +-
avro/src/schema.rs | 417 +++++++++++----------
.../{avro-rs-219.rs => avro_schema_component.rs} | 32 +-
avro_derive/src/lib.rs | 18 +-
avro_derive/tests/derive.rs | 2 +-
8 files changed, 263 insertions(+), 226 deletions(-)
copy avro/tests/{avro-rs-219.rs => avro_schema_component.rs} (60%)
