The GitHub Actions job "Fory CI" on fory.git/main has succeeded. Run started by GitHub user pandalee99 (triggered by pandalee99).
Head commit for run: 266af2a133c12dd2d235f4f47ebd66afd54bf0b8 / Zhong Junjie <[email protected]> feat(go): add type meta encoding for meta share (#2554) <!-- **Thanks for contributing to Fory.** **If this is your first time opening a PR on fory, you can refer to [CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).** Contribution Checklist - The **Apache Fory** community has requirements on the naming of pr titles. You can also find instructions in [CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md). - Fory has a strong focus on performance. If the PR you submit will have an impact on performance, please benchmark it first and provide the benchmark result here. --> ## Why? <!-- Describe the purpose of this PR. --> type forward/backward compatible serialization is critical for online service which different service update their data schema and deploy at different time. encoding format can address this : [type def encoding spec](https://fory.apache.org/docs/specification/fory_xlang_serialization_spec#type-def) ## What does this PR do? This PR implements type definition encoding and decoding that conforms to the specification. This functionality can be integrated into the main serialization flow to enable metadata sharing mode. TODOs: - Add encoding support for collection types (map, slice, set, etc.) - Integrate into the main flow to enable metadata sharing - Add support for compressed type definitions ## Related issues <!-- Is there any related issue? If this PR closes them you say say fix/closes: - #xxxx0 - #xxxx1 - Fixes #xxxx2 --> #2192 ## Does this PR introduce any user-facing change? <!-- If any user-facing interface changes, please [open an issue](https://github.com/apache/fory/issues/new/choose) describing the need to do so and update the document if necessary. Delete section if not applicable. --> - [x] Does this PR introduce any public API change? **no** - [x] Does this PR introduce any binary protocol compatibility change? **no** ## Benchmark <!-- When the PR has an impact on performance (if you don't know whether the PR will have an impact on performance, you can submit the PR first, and if it will have impact on performance, the code reviewer will explain it), be sure to attach a benchmark data here. Delete section if not applicable. --> Report URL: https://github.com/apache/fory/actions/runs/17396500692 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
