[Swagger Linter Migration] ExtensionResourcePathPattern -> use-scope-for-extension-routing by msyyc · Pull Request #5684 · Azure/typespec-azure

Yuchao Yan (msyyc) · 2026-10-13T10:30:32Z

Review fixes and current-main integration (2026-10-20)

Published fixes: afe5f3c
and d50459d.
Merged Azure main 2cd8ba15594de155ae4c79719d7e796577ccdcd7 normally and resolved
the registration/reference conflicts, preserving main's new rules and this rule.

Removed the enable/disable tutorial, introductory disable recommendation and
project-wide suppression workaround, including matching ARM guide/release-note
recommendations. Applicability is now handled through supported rule selection:
ARM library all enables all other registered rules but not this RPaaS-only policy;
the central Azure resource-manager ruleset also leaves it disabled. Explicit RPaaS
selection remains functional. No deployment detector, new identifier, source-rule
repair, diagnostic or semantic-listener change was introduced. Existing feature
release notes and the manual matrix describe the final opt-in policy.

Fresh validation at this head: ARM dependency-closure build/production typecheck;
538 ARM tests in 74 files; 7 Azure ruleset tests; root pnpm format then
pnpm lint; ARM documentation regeneration; Chronus status and diff checks.
The new applicability regression failed before the fix (unintended target warning
under ARM all) and passes afterward, with explicit selection still producing
exactly one target warning and every other registered rule remaining enabled.
Actual published examples were executed once using the document's standard ARM
imports/usings: one expected warning at the incorrect operation versus zero
diagnostics for the correct example. This is a one-time receipt, not continuous
Markdown coverage or standalone-program evidence. Documentation regeneration
retains existing unrelated missing-documentation warnings.
Final-head CI is tracked separately; these local results do not claim CI approval.

Original Swagger linter

linter code: ExtensionResourcePathPattern
linter doc: extension-resource-path-pattern.md

The original R4038 rule is an RPaaS-routing policy, not a restriction on all ARM extension-resource endpoints:

Run when the caller selects OpenApiTypes.rpaas (RPaaSViolation), rather than inferring the service's deployment audience from its paths.
Inspect the path keys selected by $.paths.
Compare the first and last occurrence of the literal, case-sensitive /providers/ segment.
Report an error at the offending emitted path when those occurrences differ: the path embeds a parent scope instead of accepting arbitrary scope.
Accept paths with zero or one matching segment and report once per path, not once per HTTP verb.

The check does not need provider-namespace metadata, schema/reference inspection, or a per-verb predicate. The retained catalog's Both classification reflects legacy common-rule extraction, not the native policy's intended audience. Supported ordinary ARM specific-parent extension endpoints are not defects merely because they contain two provider segments.

Source TypeSpec lintdiff rule

This promotes ExtensionResourcePathPattern / tsp-lintdiff-local-linter/extension-resource-path-pattern, with canonical validator slug extension-resource-path-pattern.

Original source rule: extension-resource-path-pattern.ts
Development PR: [WIP][Swagger Linter Development] ExtensionResourcePathPattern #5682.
Source repository and branch: Azure/typespec-azure, lintdiff-extension-resource-path-pattern.
Immutable reviewed and pushed source commit: 99d04f1c7311c5919993dfbb0b0a8d8168d9ce70.
Source worktree: C:\dev\worktrees\lintdiff-extension-resource-path-pattern; clean, without uncommitted rule changes.

The source is assumed done for this promotion after its clean development review. It was not modified during promotion. Independent local promotion review verified non-trivia-token equality for the operation listener, helper, diagnostic message, and severity.

Destination analysis

The agent-selected destination is @azure-tools/typespec-azure-resource-manager, under the official name use-scope-for-extension-routing. The policy governs ARM extension templates used for RPaaS routing, including the contrast between Extension.Read<Extension.ExternalResource<...>, Resource> and Extension.Read<Extension.ScopeParameter, Resource>.

Azure Core is a plausible alternative based solely on the compiler/HTTP imports, but this is not a shared REST or data-plane requirement. TCGC is not appropriate: the check concerns the authoring contract's path, not SDK naming or SDK-specific metadata. Production imports remain compiler and HTTP only, with no emitter, OpenAPI, TCGC, generated-reference inference, or unsafe mutation.

Promoted native behavior and enablement

The rule visits concrete semantic operations, resolves their paths through getHttpOperation, and warns when the path contains more than one literal /providers/ segment. It reports one warning on each offending operation, even for three segments; separate verbs on the same path can therefore produce separate warnings.

The reviewed source's template guards are preserved: uninstantiated operation templates and operations in declaration-only generic interfaces are skipped, while concrete instantiated or inherited endpoints remain checked. It checks the supplied program, not a latest-version projection or reconstructed historical Swagger.

This RPaaS-specific rule is opt-in. The ARM library's custom all ruleset enables every other registered rule and leaves use-scope-for-extension-routing disabled. Managed RPaaS configurations can select it explicitly; the separate general Azure resource-manager ruleset also leaves it disabled.

The routing policy applies to RPaaS extension-routing contracts, not ordinary ARM endpoints. Applicability is handled by rule selection rather than by an unsupported deployment detector or project-disable recipe. Ordinary ARM contracts retain supported specific-parent routes without enabling this policy. This is a destination enablement adaptation; the immutable source listener, literal path predicate, severity and diagnostic target are unchanged.

Promotion adaptations are the official name/export/description, native compiler fileRef documentation metadata and documentation URL, official registration, and native tests/docs. The semantic listener/helper, warning severity, diagnostic message, and operation targeting are unchanged. The new authored documentation includes actual ARM-template incorrect/correct examples, Impact, Suppression, and dedicated LintDiff provenance; official references were regenerated and the manual ARM matrix updated. Generated ignored website rule pages are not force-added.

Fixture-to-native test mapping

No validator or lintdiff snapshots were copied into the official package.

Original lintdiff fixture	Native vitest case	Coverage note
incorrect-extension-path	`it("targets a hardcoded-parent operation without provider-namespace metadata")`	Violating resolved path and exact operation target; no unnecessary provider guard.
scope-based-extension-path	`it("accepts an arbitrary scope with one provider segment")`	Compliant arbitrary-scope path.
template-specific-parent	`it("warns for the standard specific-parent ARM extension template")`	Standard specific-parent ARM template fixture; not a Markdown-extraction test.
template-scope	`it("accepts the standard arbitrary-scope ARM extension template")`	Standard arbitrary-scope ARM template fixture.
N/A (review regression)	`it("reports only the instantiated endpoint from a generic interface")`	Inherited concrete endpoint checked exactly once.
N/A (review regression)	`it("still reports an instantiated operation template endpoint")`	Concrete instantiated endpoint and exact diagnostic target preserved.
N/A (native contract)	`it("reports three provider segments only once")`	One diagnostic per operation rather than per segment.
N/A (native contract)	`it("reports separate operations sharing one HTTP path")`	Per-operation rather than per-emitted-path diagnostic population.
N/A (native contract)	`it("matches literal lowercase provider segments, not lookalikes")`	Literal, case-sensitive matching.
N/A (native contract)	`it("reports each distinct hardcoded-parent path")`	Separate offending paths each produce a diagnostic.
N/A (official registration)	`it("keeps only RPaaS-specific routing outside the general ARM all ruleset")`	Every other registered rule remains enabled; only the RPaaS-specific policy is excluded.
N/A (official enablement)	`it.each([false, true])("selects RPaaS routing explicitly rather than through ARM all: %s")`	Compiler integration produces no target warning under ARM `all` alone and exactly one when the rule is explicitly selected.
N/A (framework-only coverage removed)	Not ported (compiler-owned project-disable behavior)	Registration and the concrete RPaaS applicability regression remain covered.
N/A (official rulesets adaptation)	`it("keeps RPaaS extension-routing guidance opt-in in the general Azure rulesets")`	Separate general Azure rulesets do not enable the new rule.

An additional native case covers routes without provider segments. Lintdiff-specific comparison-config infrastructure is not ported: it configures the migration harness rather than implementing the official rule.

Migration evidence and limits

See the source migration.md for the native contract, focused fixtures, selected populations, real-service observations, compile failures, and uncertainty.

The retained source corpus attempted 468 projects: 462 succeeded and 6 failed, with 59,809 all-rule diagnostics. The target rule has 0 validator / 0 native findings in the ordinary-ARM, generic-all-disabled context. This is not RPaaS corpus parity. Historical unchanged-failed-set evidence is not a fresh pre-edit A/B comparison. The installed validator engine 2.2.6 and metadata checkout 6243cb01 do not establish identical research-source identity for the historical 1198225... links, whose commit was not available in the local shared checkout.

Per-authored-operation diagnostics and supplied-program version coverage intentionally differ from Swagger's per-emitted-path/latest-selected-version population. The corpus is observational source evidence, not proof of universal functional equivalence or a fresh promotion experiment.

Validation

Historical generated-all experiment (superseded)

The following records an earlier design, not the final policy. The current opt-in correction and fresh validation are recorded at the top of this description.

Removed the custom ARM library all override without changing the rule listener, diagnostic, or severity.
Updated authored documentation, manual ARM matrix, and feature change note for generated-all enablement and explicit project disablement.
ARM build passed.
Focused rule/registration suite passed: 14 tests.
Complete ARM suite passed: 488 tests in 68 files.
General Azure rulesets suite passed: 6 tests; its opt-in assertion now checks only those rulesets, not ARM library all.
Repository-wide pnpm format and pnpm lint passed; unrelated formatter-only changes were excluded.
ARM documentation regeneration completed with existing unrelated missing-documentation warnings.

Historical promotion validation

The following records the earlier promotion run, not a fresh rerun or a claim about the current test layout:

ARM dependency closure built once when the prepared checkout lacked outputs.
ARM package build and configured package lint passed.
Focused native suite passed: 17 tests.
Complete ARM suite passed: 491 tests in 67 files, including the focused rule/documentation cases.
Rulesets build, configured lint, and complete suite passed: 6 tests.
Required ARM documentation regeneration completed; the new rule's authored docs were loaded. Remaining generator warnings concern existing unrelated documentation.
Explicit-file Prettier write/check passed for authored files, generated README/reference/rule page, and the manual ARM matrix, using the empty-ignore override for generated docs.
Separate destination feature and disabled-registration rulesets internal Chronus entries were validated with LF line endings and chronus status.
Complete file scope, source provenance, unchanged validation/configuration fingerprints, and git diff --check passed.
Independent persistent local promotion precommit review: clean. Separate postpublication GitHub review remains pending.

Repository-wide validate:pr and website build were predeclared unwarranted for this scoped promotion and were not run; CI owns the authoritative website build. No required check remains failed or incomplete.

Promotion sync policy

The clean-reviewed development head remains the source of semantic truth. A source-semantic defect discovered in promotion review blocks this PR and returns evidence to the owning queue for an authorized bounded development repair. Promotion resumes from a new immutable source pin only after clean source review; it does not repair source semantics solely in the official copy.

Review follow-up (2026-10-16)

Removed the compiler-owned project-disable test only. Retained rule registration, actual generated-all activation, concrete endpoint coverage, the separate disabled central-ruleset policy, and opt-out docs. Current focused rule/registration suites: 13 passed. Repository format/lint and diff check passed. Earlier suite counts below describe historical revisions.

Current-main compatibility (2026-10-16, `111999c`)

Merged main 88d691bb5 normally in 111999c35. The ruleset-test resolution retains both the central-ruleset opt-in assertions and main's redundant-summary assertion; rule IDs and enablement are unchanged.

After merging: dependency-closure build, 13 focused ARM tests and 7 ruleset tests, repository format/lint and uncached formatting checks passed. Dependency-closure build passed; a separate full test-project tsc was not run. Fresh required CI checks at this head are pending; the historical checks above do not establish current-head readiness.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

github-actions · 2026-10-13T10:33:34Z

All changed packages have been documented.

✅ @azure-tools/typespec-azure-resource-manager
✅ @azure-tools/typespec-azure-rulesets

Show changes

`@azure-tools/typespec-azure-resource-manager` - feature ✏️

Add the opt-in use-scope-for-extension-routing rule for managed RPaaS extension-routing contracts. The rule requires arbitrary-scope paths rather than hardcoded parent paths. ARM library all does not enable this RPaaS-specific policy; specific-parent extension paths remain supported for ordinary ARM contracts.

`@azure-tools/typespec-azure-rulesets` - internal ✏️

Register @azure-tools/typespec-azure-resource-manager/use-scope-for-extension-routing as disabled in the general ARM ruleset.

github-actions · 2026-10-13T10:36:58Z

📦 Package size report

✅ No notable package size changes compared to the base branch.

14 package(s) with no notable change

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
`@azure-tools/typespec-azure-rulesets`	5.60 KB → 5.96 KB	+371 B (+6.5%)	34.59 KB → 34.80 KB	+213 B (+0.6%)
`@azure-tools/typespec-azure-resource-manager`	188.18 KB → 188.38 KB	+214 B (+0.1%)	1.13 MB → 1.13 MB	+1.09 KB (+0.1%)
`@azure-tools/azure-http-specs`	143.53 KB → 143.53 KB	—	1.20 MB → 1.20 MB	—
`@azure-tools/typespec-autorest`	87.87 KB → 87.87 KB	—	424.17 KB → 424.17 KB	—
`@azure-tools/typespec-autorest-canonical`	7.42 KB → 7.42 KB	—	26.00 KB → 26.00 KB	—
`@azure-tools/typespec-azure-core`	136.55 KB → 136.55 KB	—	733.30 KB → 733.30 KB	—
`@azure-tools/typespec-azure-examples`	80.15 KB → 80.15 KB	—	383.36 KB → 383.36 KB	—
`@azure-tools/typespec-azure-portal-core`	36.26 KB → 36.26 KB	—	242.62 KB → 242.62 KB	—
`@azure-tools/typespec-client-generator-core`	248.24 KB → 248.24 KB	—	1.32 MB → 1.32 MB	—
`@azure-tools/typespec-go`	263.76 KB → 263.76 KB	—	1.35 MB → 1.35 MB	—
`@azure-tools/typespec-java`	20.22 MB → 20.22 MB	—	22.51 MB → 22.51 MB	—
`@azure-tools/typespec-metadata`	15.91 KB → 15.91 KB	—	62.26 KB → 62.26 KB	—
`@azure-tools/typespec-python`	42.58 KB → 42.58 KB	—	166.02 KB → 166.02 KB	—
`@azure-tools/typespec-ts`	530.76 KB → 530.76 KB	—	2.67 MB → 2.67 MB	—

_{Packed = gzipped .tgz published to npm. Unpacked = total extracted size. 🆕 added, 🗑️ removed. Packages from the core/ submodule are not included.
🔴 grew · 🟢 shrank — only changes of at least 512 B and 0.5% are marked.}

pkg-pr-new · 2026-10-13T10:37:36Z

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/typespec-azure-resource-manager@5684

npm i https://pkg.pr.new/@azure-tools/typespec-azure-rulesets@5684

commit: b1467bf

Copilot

🟡 Changes recommended

The rule documentation must use the repository-required canonical R4038 LintDiff link.

1 open finding

Link R4038 to the canonical OpenAPI authoring guideline · New

What changed in this PR

Adds an opt-in ARM linter rule enforcing scope-based RPaaS extension routing while preserving ordinary ARM behavior.

Changes:

Implements and registers the rule, disabled by default.
Adds comprehensive rule and enablement tests.
Adds documentation, ruleset registration, and Chronus entries.

File	Description
`packages/typespec-azure-resource-manager/src/rules/use-scope-for-extension-routing.ts`	Implements the rule.
`packages/typespec-azure-resource-manager/test/rules/use-scope-for-extension-routing.test.ts`	Tests behavior and opt-in enablement.
`packages/typespec-azure-resource-manager/src/rules/use-scope-for-extension-routing.md`	Documents usage and migration provenance.
`packages/typespec-azure-resource-manager/src/linter.ts`	Registers the disabled-by-default rule.
`packages/typespec-azure-resource-manager/README.md`	Lists the new rule.
`packages/typespec-azure-rulesets/src/rulesets/resource-manager.ts`	Explicitly disables it in the general ruleset.
`packages/typespec-azure-rulesets/test/validate-rules-defined.test.ts`	Verifies opt-in status.
`website/src/content/docs/docs/libraries/azure-resource-manager/reference/linter.md`	Updates generated reference documentation.
`website/src/content/docs/docs/howtos/ARM/arm-rules.md`	Adds the ARM rule matrix entry.
`.chronus/changes/arm-use-scope-for-extension-routing-2026-10-13.md`	Records the ARM package feature.
`.chronus/changes/arm-use-scope-for-extension-routing-ruleset-2026-10-13.md`	Records ruleset registration.

🧠 Review effort: Balanced

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

azure-sdk-automation · 2026-10-13T10:51:38Z

You can try these changes here

🛝 Playground	🌐 Website

Timothee Guerin (timotheeguerin) · 2026-10-13T18:36:09Z

Copilot-generated review feedback.

Could we reconcile the inline templated-interface guard with the existing ARM isTemplatedInterfaceOperation helper in src/rules/utils.ts, rather than adding another interpretation?

The existing helper checks the operation's declaration node as well as whether its interface is an uninstantiated template; this PR checks the interface directly. Other migration rules import the helper, while #5526 duplicates it locally.

This should not be a blind substitution: first establish which concrete/inherited/template operations this rule must check and whether the node-kind distinction matters, then reuse or improve the shared helper accordingly. Avoid adding a universal operation-skip wrapper that conflates template declarations, template instances, service membership, and project-location filtering.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yuchao Yan (msyyc) · 2026-10-14T06:10:47Z

Follow-up to this review feedback.

Reused the existing package-private isTemplatedInterfaceOperation helper while retaining this rule's finished-type eligibility check. Existing routing/template behavior remains covered by the focused suite. Also replaced Markdown fence-reading assertions with ordinary TypeSpec fixtures.

Implemented in 5e30d542b. Scoped formatting, type-aware lint, package build and the focused native tests passed. Review threads are intentionally left open.

## Summary Make subsequent RPaaS migrations smoother without broadening RPaaS restrictions to ordinary ARM or weakening validation/recovery gates. This is a standalone, skill-only follow-up to the first `ExtensionResourcePathPattern` migration in #5682 and promotion in #5684. ## Process findings and changes | Observed evidence | Skill correction | | --- | --- | | Intake initially stopped because no automatic native RPaaS selector was established. The accepted continuation used existing explicit lint enablement, default-disabled, with ordinary ARM counterexamples. Upstream RPaaS registration had been flattened to catalog `common`/`Both`. | Establish upstream audience separately from catalog eligibility. Consider supported native selection, an independently justified broader guideline, or documented external opt-in before classifying. Record mixed-audience limitations; preserve genuine uncertainty stops. | | The full generic corpus selected 468 projects, compiled 462, and left six failures. Target `0/0` reflected a default-disabled rule and ordinary ARM selection, not RPaaS parity. | Carry actual validator/native activation profiles into migration notes, promotion, and both reviews. Require enabled focused evidence and appropriate activation integration controls; retain required representative/full regression runs and disclose audience, version, diagnostic-unit, and source-identity limits. | | Development review reproduced two warnings for one authored operation-template endpoint, including a template companion. Four focused regressions corrected the diagnostic unit. | Check rule-owned HTTP/template traversal and exact endpoint counts/targets before expensive corpus runs, while retaining the exclusion of framework-only tests. | | Promotion documentation regeneration exited successfully but did not load the authored rule Markdown until supported compiler `docs`/`fileRef` metadata was added. | Verify authored-file binding and generated rationale/examples, not merely a successful regeneration or index entry. | | A quiet successful lint command produced no `Tee-Object` receipt file. Guessed config paths and a stale readiness budget mirror also caused avoidable handoff failures. | Capture empty raw output independently, derive paths from the actual checkout, and acknowledge authoritative later scoped grants without inventing stale-mirror prerequisites. Preserve exit statuses, counters, fingerprints, and failed evidence. | The reusable audience contract lives in rule intake; development, queue handoffs, and promotion link to it rather than duplicating a new RPaaS detector. Promotion also checks library/default/recommended/`all` activation, including automatic `all` behavior, and preserves every existing rule's enablement. ## Evidence and boundaries - The reviewed source's [migration evidence](https://github.com/Azure/typespec-azure/blob/99d04f1c7311c5919993dfbb0b0a8d8168d9ce70/packages/typespec-lintdiff/test/fixtures/ExtensionResourcePathPattern/migration.md) documents the native opt-in contract, ordinary ARM scope distinction, template regression, corpus limitations, and intentional diagnostic-unit/version differences. - The original stop, accepted continuation, failed-command receipts, scoped grants, and handoffs remain in the coordinating session's durable process records. Those operational artifacts are not committed. - Existing capabilities/reviewer ownership, immutable-source review, finite recovery authorization, and `no-valid-comments` termination already cover the runtime/review portions of the run and remain unchanged. The earlier optional `.git` repository-identity clarification remains separate in #5685. - No rule/package files, completed migration commits, later promotion changes, catalog schema, new worker flags, production audience detectors, dependencies, release entries, or generated outputs are changed. This PR does not claim production RPaaS corpus parity or re-review subsequent rule-PR heads. ## Validation - Reviewed the complete six-file Markdown diff against fetched canonical `feature/lintdiff-migration-new` base `527a585925e61bd782e61cce9127e235e555ea91`, including linked native-test responsibility and recovery/ownership contracts. - Ran Prettier write/check on only the six explicit changed files using already-prepared repository tooling; all passed. - Verified 76 relative Markdown file references and all new audience-contract anchors. - `git diff --check` passed. - No dependency installation, submodule setup, package/corpus builds/tests, repository-wide formatting, or recursive review loop was needed for this documentation-only update. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

## Evidence During the ExtensionResourcePathPattern queue, a publication preflight rejected the verified canonical remote https://github.com/Azure/typespec-azure solely because it lacked a .git suffix (command103). GitHub repository identity and push permission were already established, the reviewed content was unchanged, and no publication operation had been attempted. Independent read-only reconciliation confirmed the existing binding and permitted the next authorized action. ## Change Clarify the shared publication preflight: the optional .git suffix does not change the resolved owner/repository. Preserve actual effective push URL/refspec recording, canonical GitHub metadata and permission checks, phase ownership, and all duplicate-safe recovery rules. This does not authorize retries or weaken any content, review, validation, or publication gate. ## Scope and validation One skill-documentation file only, on a dedicated branch based on the freshly fetched canonical feature/lintdiff-migration-new ref. Explicit-file Prettier and git diff --check passed. The initial fresh-worktree formatter could not load the absent core plugin; the existing prepared promotion formatter/config was used instead, with no dependency installation or submodule setup. No rule/package/corpus changes or generated artifacts. Primary PRs #5682 and #5684 are untouched. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Simplify distinct path diagnostics and remove runtime enablement repetition while retaining opt-in registration in the configuration suite. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…tern

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Remove the custom all override, cover inherited enablement and explicit disablement, and align routing guidance. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…tern

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Preserve extension-routing policy coverage alongside current main rule registrations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…tern

State RPaaS applicability directly and remove project-level enable/disable recipes from authoring guidance. Preserve current rule registration pending a managed applicability decision. Retain main and migration rule registrations in merge resolutions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Promote opt-in RPaaS extension routing lint to ARM

af49655

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

microsoft-github-policy-service Bot added int:azure-specs Run integration tests against azure-rest-api-specs lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library meta:website TypeSpec.io updates linter Issues related to linter rules labels Oct 13, 2026

Yuchao Yan (msyyc) requested a balanced review from Copilot October 13, 2026 10:37

Copilot started reviewing on behalf of Yuchao Yan (msyyc) October 13, 2026 10:37

View session

Copilot AI reviewed Oct 13, 2026

View reviewed changes

Comment thread packages/typespec-azure-resource-manager/src/rules/use-scope-for-extension-routing.md

Yuchao Yan (msyyc) mentioned this pull request Oct 13, 2026

Clarify canonical Git remote URL identity #5685

Merged

Yuchao Yan (msyyc) mentioned this pull request Oct 13, 2026

Migrate ARM swagger linter rule to typespec linter rule #5274

Open

refactor(arm): reuse extension routing guard and link ARM guideline

5e30d54

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yuchao Yan (msyyc) mentioned this pull request Oct 14, 2026

docs(skills): preserve RPaaS audience across lint migrations #5702

Merged

Yuchao Yan (msyyc) marked this pull request as ready for review October 14, 2026 07:08

Yuchao Yan (msyyc) requested review from Mark Cowlishaw (markcowl), Timothee Guerin (timotheeguerin) and Jeff Fisher (xirzec) as code owners October 14, 2026 07:08

Yuchao Yan (msyyc) and others added 2 commits October 14, 2026 17:30

test(arm): separate extension routing and linter configuration coverage

3672c2b

Simplify distinct path diagnostics and remove runtime enablement repetition while retaining opt-in registration in the configuration suite. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Merge branch 'main' into promote-lintdiff-extension-resource-path-pat…

8f99391

…tern

Timothee Guerin (timotheeguerin) reviewed Oct 14, 2026

View reviewed changes

Comment thread packages/typespec-azure-resource-manager/test/rules/use-scope-for-extension-routing.test.ts Outdated

Timothee Guerin (timotheeguerin) reviewed Oct 14, 2026

View reviewed changes

Comment thread packages/typespec-azure-resource-manager/src/linter.ts

Remove vacuous extension-routing template declaration tests

ee0e351

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yuchao Yan (msyyc) requested a review from Timothee Guerin (timotheeguerin) October 15, 2026 07:28

Yuchao Yan (msyyc) and others added 2 commits October 15, 2026 16:56

Use generated ARM all ruleset for extension routing

39110c3

Remove the custom all override, cover inherited enablement and explicit disablement, and align routing guidance. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Merge branch 'main' into promote-lintdiff-extension-resource-path-pat…

5a3527b

…tern

Timothee Guerin (timotheeguerin) reviewed Oct 15, 2026

View reviewed changes

Comment thread packages/typespec-azure-resource-manager/test/linter.test.ts Outdated

Yuchao Yan (msyyc) and others added 2 commits October 16, 2026 10:06

test(arm): keep extension-routing coverage package-specific

2f07d77

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore: merge main into extension-routing migration

111999c

Preserve extension-routing policy coverage alongside current main rule registrations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Timothee Guerin (timotheeguerin) reviewed Oct 16, 2026

View reviewed changes

Comment thread .chronus/changes/promote-lintdiff-extension-resource-path-pattern-2026-9-16-10-0-12.md Outdated

Timothee Guerin (timotheeguerin) reviewed Oct 16, 2026

View reviewed changes

Comment thread .chronus/changes/review-extension-route-template-guard.md Outdated

chore(arm): keep one extension routing release entry

f20d241

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yuchao Yan (msyyc) requested a review from Timothee Guerin (timotheeguerin) October 19, 2026 04:56

Merge branch 'main' into promote-lintdiff-extension-resource-path-pat…

b47ffd6

…tern

Timothee Guerin (timotheeguerin) reviewed Oct 19, 2026

View reviewed changes

Comment thread packages/typespec-azure-resource-manager/src/rules/use-scope-for-extension-routing.md Outdated

Timothee Guerin (timotheeguerin) reviewed Oct 19, 2026

View reviewed changes

Comment thread packages/typespec-azure-resource-manager/src/rules/use-scope-for-extension-routing.md Outdated

Yuchao Yan (msyyc) and others added 3 commits October 20, 2026 13:40

Keep RPaaS extension routing opt-in in ARM rulesets

d50459d

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore: remove redundant extension-routing ruleset changelog

b1467bf

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Navigation Menu

Repository navigation

[Swagger Linter Migration] ExtensionResourcePathPattern -> use-scope-for-extension-routing - #5684

[Swagger Linter Migration] ExtensionResourcePathPattern -> use-scope-for-extension-routing#5684
Yuchao Yan (msyyc) wants to merge 14 commits into
mainfrom
promote-lintdiff-extension-resource-path-pattern

Yuchao Yan (msyyc) commented Oct 13, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 13, 2026 •

edited

Loading

`@azure-tools/typespec-azure-resource-manager` - feature ✏️

`@azure-tools/typespec-azure-rulesets` - internal ✏️

Uh oh!

github-actions Bot commented Oct 13, 2026 •

edited

Loading

Uh oh!

pkg-pr-new Bot commented Oct 13, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

azure-sdk-automation Bot commented Oct 13, 2026

Uh oh!

Timothee Guerin (timotheeguerin) commented Oct 13, 2026

Uh oh!

Yuchao Yan (msyyc) commented Oct 14, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

Yuchao Yan (msyyc) commented Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review fixes and current-main integration (2026-10-20)

Original Swagger linter

Source TypeSpec lintdiff rule

Destination analysis

Promoted native behavior and enablement

Fixture-to-native test mapping

Migration evidence and limits

Validation

Historical generated-all experiment (superseded)

Historical promotion validation

Promotion sync policy

Review follow-up (2026-10-16)

Current-main compatibility (2026-10-16, 111999c)

Uh oh!

github-actions Bot commented Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

@azure-tools/typespec-azure-resource-manager - feature ✏️

@azure-tools/typespec-azure-rulesets - internal ✏️

Uh oh!

github-actions Bot commented Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📦 Package size report

Uh oh!

pkg-pr-new Bot commented Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Uh oh!

azure-sdk-automation Bot commented Oct 13, 2026

Uh oh!

Timothee Guerin (timotheeguerin) commented Oct 13, 2026

Uh oh!

Yuchao Yan (msyyc) commented Oct 14, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Yuchao Yan (msyyc) commented Oct 13, 2026 •

edited

Loading

Current-main compatibility (2026-10-16, `111999c`)

github-actions Bot commented Oct 13, 2026 •

edited

Loading

`@azure-tools/typespec-azure-resource-manager` - feature ✏️

`@azure-tools/typespec-azure-rulesets` - internal ✏️

github-actions Bot commented Oct 13, 2026 •

edited

Loading

pkg-pr-new Bot commented Oct 13, 2026 •

edited

Loading