Web Console 1.6.164: localize Receiver validation labels - #147
Merged
Merged
Conversation
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
1 participant
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.
Scope: exactly the reviewed 13 files. Receiver and its three supported driver configurations reuse existing visible labels in shared required/numeric errors; model-specific labels keep precedence and unknown fields retain fallback. The two scale min-greater-than-max conditions are unchanged, with existing localized numeric copy. No API/schema/permission/driver behavior, dependency graph or security threshold changes. Package/lock root versions and dependent gate literals are synchronized to 1.6.164. Focused native Chrome 153 validation passed 12/12 cases and 61/61 assertions, including eight new Receiver cases and four existing validation cases. The initial fixture-precedence failure is retained separately. Official exact-head validate and required CodeQL are pending; this PR is not component publication, QA deployment, full-language or complete-matrix PASS. Published 1.6.163 and earlier HOLD evidence remain unchanged.