Summary
No CI check builds or tests the generator; add a pipeline that runs the unit tests, the parity gate, and compiles generated output against a real kiota client.
What's working now
Locally: 100+ unit tests, a parity gate against the published inventory, and a packagingpipeline that has already caught eight generator bugs by compiling real modules.
How can we make it better
Pull requests into powershell-v3 currently execute zero generator checks (ci-build.yml triggers only on main and never touches tools/WrapperGenerator). Add a pipeline, path-filtered to tools/WrapperGenerator**, that runs the tests, generates a pilot module,
runs the parity gate, and compiles wrappers against a freshly generated kiota client. The compile step is the only automatic defense against kiota-prediction drift.
Summary
No CI check builds or tests the generator; add a pipeline that runs the unit tests, the parity gate, and compiles generated output against a real kiota client.
What's working now
Locally: 100+ unit tests, a parity gate against the published inventory, and a packagingpipeline that has already caught eight generator bugs by compiling real modules.
How can we make it better
Pull requests into powershell-v3 currently execute zero generator checks (ci-build.yml triggers only on main and never touches tools/WrapperGenerator). Add a pipeline, path-filtered to tools/WrapperGenerator**, that runs the tests, generates a pilot module,
runs the parity gate, and compiles wrappers against a freshly generated kiota client. The compile step is the only automatic defense against kiota-prediction drift.