Repository navigation
Fix repeated-path-info for concrete inherited PUT operations - #5788
Merged
Yuchao Yan (msyyc) merged 1 commit intoOct 22, 2026
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Yuchao Yan (msyyc)
requested review from
Mark Cowlishaw (markcowl),
Timothee Guerin (timotheeguerin) and
Jeff Fisher (xirzec)
as code owners
October 21, 2026 09:57
5 tasks done
Yuchao Yan (msyyc)
merged commit Oct 22, 2026
2d8c19e
into
feature/lintdiff-migration-new
2 checks passed
Yuchao Yan (msyyc)
deleted the
fix/lintdiff-repeated-path-info-inherited-20261021
branch
October 22, 2026 03:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bounded source repair for #5526
The original source migration #5523 is merged. This separately authorized follow-up fixes its concrete inherited-operation boundary without reopening that PR or mutating the original reviewed source pin
08ea9770a0209d7a131c467ec0fd93f3918b1714. The source package exists on the owning development queue, so this repair targetsfeature/lintdiff-migration-new, notmain. No merge is requested or performed automatically.isTemplateInstance(operation)also matches real PUT endpoints inherited from generic interfaces into concrete interfaces. The canonical violating regression previously produced zero warnings instead of one. Use the compiler's declaration-aware predicate, retain genuine template exclusions, and add inherited positive/negative controls with an exact authored-property diagnostic target. Rule identity, message, enablement and authored-vs-JSON-name semantics are unchanged. Source migration guidance and its unreleased fix note match this boundary.Validation and review
a6137cac43a727ce0c2656364fd72d50c272ee4a.0ac45147f27cf61f439bcd3778eafb6e4b7d08f3; the committed tree is identical. The reviewer independently reran all 14 focused tests. This is not GitHub approval.Root lint is not green: it reports 228 warnings entirely in unchanged harness/other-rule files, zero in the changed source/test. Root formatting rewrote unrelated baseline fixture/metadata files; only formatter-owned spillover was restored, and the final diff is exactly five intended files. Narrow checks follow the repository's generated-artifact/baseline exception. Historical corpus totals were not refreshed and are not claimed as repaired-head evidence. No universal Swagger parity or broad integration/merge readiness is claimed.