The GitHub Actions job "Fory CI" on fory.git/main has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang).
Head commit for run: 68deb8079e3f2e34b67c2f96eae510a9db1b7a28 / Shawn Yang <[email protected]> refactor(dart): revamp runtime API and unify codegen naming (#3323) ## Why? - Align Dart runtime API naming with pyfory style. - Simplify configuration and registration flows. - Normalize naming across runtime/codegen layers for maintainability. ## What does this PR do? - Updates the Dart public runtime API: - `Fory(refTracking: ...)` -> `Fory(ref: ...)`, and adds `stringRefIgnored`. - `toFory` / `fromFory` / `toForyWithWriter` -> `serialize` / `deserialize` / `serializeTo`. - `register(spec, tagOrTypeId)` -> named registration parameters (`typeId`, `namespace`, `typename`) with `registerType`, `registerClass`, and `registerEnum` helpers. - `Furiable` / `$foryType` -> `ForyTypeProvider` / `foryType`. - Refactors Dart internals: - Removes `BaseFory` and `ForyConfigManager`. - Converts `ForyConfig` into an immutable value config. - Renames coordinator/resolver/runtime symbols to normalized names (for example `XtypeResolver` -> `TypeResolver`, `SerializeCoordinator` -> `SerializationRuntime`). - Renames multiple files/classes to remove abbreviations and keep naming consistent. - Updates docs/examples/tests to the new API and naming across `dart/README.md`, package examples, and Dart test suites (codegen, cross-language, buffer/datatype/perf). ## Related issues N/A ## 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 N/A Report URL: https://github.com/apache/fory/actions/runs/21897858816 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
