[release/10.0-preview6] Fix PropertyGetter to handle value types correctly in SupplyParameterFromPersistentComponentStateValueProvider #62395
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
… tests Co-authored-by: javiercn <[email protected]>
…orks correctly Co-authored-by: javiercn <[email protected]>
Co-authored-by: javiercn <[email protected]>
…xplicitly Co-authored-by: javiercn <[email protected]>
lewing
added
Servicing-consider
lewing
approved these changes
Jun 19, 2025
|
approving as discussed in tactics, @wtgodbe please merge |
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.
Backport of #62369 to release/10.0-preview6
/cc @javiercn @copilot
Fix PropertyGetter to handle value types correctly in SupplyParameterFromPersistentComponentStateValueProvider
Summary of the changes (Less than 80 chars)
Description
{Detail}
Fixes #{bug number} (in this specific format)
Customer Impact
{Justification}
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
[Justify the selection above]
Verification
Packaging changes reviewed?
When servicing release/2.1