Uh oh!
There was an error while loading. Please reload this page.
[release/8.0] Emit interceptor info correctly when invocation expr is on separate line - #91218
Conversation
ghost
commented
Aug 28, 2023
Tagging subscribers to this area: @dotnet/area-extensions-configuration Issue DetailsBackport of #91107 to release/8.0 /cc @layomia Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
Uh oh!
There was an error while loading. Please reload this page.
carlossanlop
commented
Aug 28, 2023
@layomia this needs M2 approval. @ericstj or @jeffhandley do you approve? |
Uh oh!
There was an error while loading. Please reload this page.
* Add comments to binding gen tests for invocations on new lines * Address feedback & test static method call syntax * Reorganize and comment the newline/whitespace scenarios * Reorganize and comment the newline/whitespace scenarios for ConfigurationExtensions --------- Co-authored-by: Jeff Handley <jeffhandley@users.noreply.github.com>
jeffhandley
left a comment
There was a problem hiding this comment.
This has my support for RC2. It fixes a bug in a new net8 feature, and we would service for this.
layomia
commented
Aug 30, 2023
@carlossanlop pls help merge. |
Backport of #91107 to release/8.0
/cc @layomia
Customer Impact
Fixes the following issue which users will definitely run into & expect to work.
Same line
Interceptor location is successfully parsed. Project compiles:
Different line
Parsed interceptor location is inaccurate. Compilation fails with a CSC interceptors error stating that the generated
[InterceptsLocation]points to an invalid location.Testing
Automated unit tests verify the fix for a wide range of permitted language syntax. Manually verified in showcase ASP.NET app.
Risk
Low. It's a small, contained fix for an off-by-default component.