The GitHub Actions job "npm_and_yarn in /javascript for minimatch - Update 
#1257593276" on fory.git/main has failed.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).

Head commit for run:
c8fd5ed5c3d463e5bdb772553a21d2ec4789af03 / Shawn Yang <[email protected]>
refactor(c#): refactor serializer interface to minimize API surface (#3403)

## Why?

`Serializer<T>` had accumulated type metadata and object-dispatch
responsibilities (type id, nullability, ref-tracking, type-info
read/write, and object-level read/write). That expanded the public
serializer API and duplicated logic across many serializer
implementations.

## What does this PR do?

- Removes the non-generic `Serializer` base and narrows `Serializer<T>`
to typed read/write responsibilities.
- Introduces richer `TypeInfo` metadata (built-in/user/dynamic kind,
nullability, ref-trackability, default object, object-level read/write
delegates, and field type-info decisions).
- Refactors `TypeResolver` to operate on `TypeInfo` for registration,
serializer factory creation/validation, wire-type resolution, and
centralized type-info read/write.
- Updates collection/dictionary/nullable-key/Any serialization flows and
generator output to use `TypeInfo` + resolver-dispatched
object/type-info operations.
- Removes repeated `StaticTypeId`/nullability/ref-tracking/`IsNone`
overrides across primitive, array, collection, dictionary, optional,
string, time, enum, and union serializers.
- Updates C# registration and peer test serializer call sites to the new
type-info driven serializer contract.

## Related issues



## Does this PR introduce any user-facing change?



- [x] Does this PR introduce any public API change?
- [ ] Does this PR introduce any binary protocol compatibility change?

## Benchmark

Report URL: https://github.com/apache/fory/actions/runs/22382792858

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to