Repository navigation
Validate unified examples against API contracts and preserve parameter locations - #5799
Timothee Guerin (timotheeguerin) wants to merge 11 commits into
Conversation
|
❌ There is undocummented changes. Run The following packages have changes but are not documented.
The following packages have already been documented:
Show changes
|
📦 Package size report2 packages changed size, +7.26 KB (+0.0%) packed overall.
12 package(s) with no notable change
Packed = gzipped |
commit: |
|
You can try these changes here
|
Unified examples can currently validate successfully even when values do not match the API, and a misspelled operation can silently lose its example during compilation.
tsp-examples validate <project>now compiles the current TypeSpec/AutoRest HTTP contract in memory and checks request/response values with the existing JSON Schema validator. Errors include the API version, offending value path, and YAML location. No generated files are overwritten.Unknown applicable operation keys are errors during both validation and AutoRest compilation. External Swagger parameter references are resolved before migrating locations or expanding body parameter names, eliminating the manual path-parameter repairs needed by every ARM pilot.
Command behavior change: API validation requires
main.tspand the project's installed compiler/AutoRest emitter. Use--schema-onlyfor format-only folders or the previous check. The pure/browser validation APIs remain format-only and unchanged.Fixes #5793, #5795, and #5796.
Targets
release/october-2026; contributor documentation is kept in a separatemainPR. Real Purview validation succeeds in strict mode; Community Training now correctly identifies its existing undeclared LRO response header.