[release/7.0] Update RateLimiting ref assembly #75978
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #75976 to release/7.0 /cc @BrennanConroy Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
BrennanConroy
added
the
Servicing-consider
ViktorHofer
removed
Servicing-consider
ghost
locked as resolved and limited conversation to collaborators
Backport of #75976 to release/7.0
/cc @BrennanConroy
Customer Impact
Customers will see that some properties are settable on a type when they shouldn't be. This doesn't cause issues in our code because we give the object to the customer for their own consumption and don't use it after. But it isn't great that we expose the properties for users to set when they aren't meant to be.
Testing
Manually verified the ref assembly has the updated information via ILSpy.
Risk
Low, no code changes, just an updated attribute on properties in the ref assembly.