Use sonic-ext:custom-validation as complexed logical range resolution.#6
Merged
Conversation
jjin62
reviewed
May 5, 2026
jjin62
left a comment
There was a problem hiding this comment.
check target-gain against configured min-gain and max-gain value
39081c5 to
0c920d0
Compare
- Introduce sonic-ext:custom-validation to support component-specific dynamic range validation - Add additional identities to extend amplifier type coverage - Use target-gain as a reference example for dynamic range enforcement - Exclude src/sonic-yang-models/common since sonic-mgmt-common already has sonic-extension.yang. Cause import conflicts
0c920d0 to
b9c6c80
Compare
jjin62
reviewed
May 8, 2026
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.
Solution for the other two use cases