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

Head commit for run:
550d8eefcab52e0364c9931abe877210b27cbd9f / Shawn Yang <[email protected]>
feat(swift): fory swift schema idl codegen (#3433)

## Why?

Swift IDL schema code generation was missing from the compiler workflow.
This PR adds Swift generation and the required runtime/test/docs
integration so Swift users can generate and validate IDL-based models
end-to-end.


## What does this PR do?

- Adds Swift as a compiler target with `--lang swift` and `--swift_out`,
plus `--swift_namespace_style` support.
- Implements `compiler/fory_compiler/generators/swift.py` to generate
Swift schema/model code (messages, enums, unions, registration helpers,
import-aware references).
- Extends compiler option handling (`swift_namespace_style`) and proto
extension options, with corresponding parser and generator plumbing.
- Adds/updates compiler tests for Swift generation, package options, and
CLI option behavior.
- Updates Swift runtime and macro logic used by generated code,
including compatible metadata/field-ID handling and related
serialization/deserialization coverage.
- Adds Swift IDL integration test package + runner script and wires
Swift/C# IDL runs into CI.
- Updates compiler and Swift documentation for Swift codegen usage and
generated code behavior.

## Related issues

Closes #3357

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

Yes. The compiler now supports Swift schema code generation and new
Swift-related CLI/config options.

- [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/22516716554

With regards,
GitHub Actions via GitBox


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

Reply via email to