Uh oh!
There was an error while loading. Please reload this page.
[Group 3] Enable nullable annotations for Microsoft.Extensions.FileProviders.Physical - #57409
Conversation
ghost
commented
Aug 14, 2021
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. |
ghost
commented
Aug 14, 2021
Tagging subscribers to this area: @maryamariyan, @dotnet/area-extensions-filesystem |
Microsoft.Extensions.FileProviders.PhysicalUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Issue to remove/review "!": dotnet#57518
- handle Microsoft.Extensions.FileProviders.Abstractions nullability annotations (dotnet/runtime#57405) - handle Microsoft.Extensions.FileProviders.Physical nullability annotations (dotnet/runtime#57409) - !fixup! improve `HttpConnectionDispatcher.GetConnectionToken(...)` and its use
[main] Update dependencies from dotnet/efcore dotnet/runtime - Respond to nullable annotations of `StringSegment` - general assumption is we don't create `StringValues` w/ `null` entries - in addition, `StringSegment.IsNullOrEmpty(StringSegment)` doesn't seem to help the compiler - !fixup! - Handle more nullable expressions - mostly about nullability annotations in `StringValues` and `StringSegment` - see dotnet/runtime#58223 for info about the `StringValues` -> `string` implicit conversion - Merge branch 'main' into darc-main-fcbf8a54-42e6-4ded-9535-034b26dfd6ba - Latest nullability updates - handle Microsoft.Extensions.FileProviders.Abstractions nullability annotations (dotnet/runtime#57405) - handle Microsoft.Extensions.FileProviders.Physical nullability annotations (dotnet/runtime#57409) - !fixup! improve `HttpConnectionDispatcher.GetConnectionToken(...)` and its use - Remove some `StringSegment.Value` `null` forgiveness and extra handling - e.g. `ResponseCompressionProvider` used `StringSegment.Value` when a `string` constant would do - also, `MediaTypeHeaderValue.Charset` getter unnecessarily did `StringSegment` -> `string` -> `StringSegment` - also, `CookieHeaderParserShared` ignored `[NotNullWhen(true)]` attributes in helper - !fixup! Handle `IsNullOrEmpty(...)` metadata lack - !fixup! Use `ToString()` instead of suppression - Update `KnownHeaders` - then regenerate HttpHeaders.Generated.cs - Do generated JS files need to change? - !fixup! Allow `Charset` to be `null` - !fixup! Adjust to fix failing tests - note `HttpResponse.ContentType` type now matches `HttpRequest.ContentType` - !fixup! React to `HttpResponse.ContentType` change
Related to #43605
Annotated according to:
Microsoft.Extensions.FileProviders.Abstractions#57405Issue to fix implementation issues: #57518