Prevent spec-derived values from escaping AutoRest output directories - #5340
Prevent spec-derived values from escaping AutoRest output directories#5340Timothee Guerin (timotheeguerin) with Copilot wants to merge 4 commits into
Conversation
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
|
Azure Pipelines: 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
commit: |
|
All changed packages have been documented.
Show changes
|
📦 Package size report✅ No notable package size changes compared to the base branch. 13 package(s) with no notable change
Packed = gzipped |
|
You can try these changes here
|
|
Copilot resolve the merge conflicts in this pull request |
…to-typespec-autorest-emitter # Conflicts: # core # pnpm-lock.yaml Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Resolved the merge conflicts against the latest |
The AutoRest emitter interpolated raw service names and API versions into filesystem paths, allowing traversal-like spec values to escape configured directories.
Path sanitization
{service-name}and{version}in output paths.Compiler integration
sanitizePathSegment.Regression coverage
The version is emitted as
.._.._.._escaped, keeping generated and example paths within their configured directories.