fix: poly sharp condition #10
Triggered via pull request
September 16, 2023 19:58
Status
Success
Total duration
1m 34s
Artifacts
–
Annotations
21 warnings
Build & Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build & Test:
SourceKit.Sample/Analyzers/CannotLinqChainAfterTerminalOperation/CodeFixerTestCases.cs#L8
Nullability of reference types in type of parameter 'x' doesn't match implemented member 'bool IEqualityComparer<T>.Equals(T? x, T? y)' (possibly because of nullability attributes).
|
Build & Test:
SourceKit.Sample/Analyzers/CannotLinqChainAfterTerminalOperation/CodeFixerTestCases.cs#L8
Nullability of reference types in type of parameter 'y' doesn't match implemented member 'bool IEqualityComparer<T>.Equals(T? x, T? y)' (possibly because of nullability attributes).
|
Build & Test:
SourceKit.Sample/Analyzers/Collections/Dictionary/KeyTypeImplementsEquatable.cs#L7
Non-nullable property 'Sample' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/Collections/Dictionary/KeyTypeDoesNotImplementEquatable.cs#L7
Non-nullable property 'Sample' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/Collections/Dictionary/CustomKeyTypeImplementsEquatable.cs#L7
Non-nullable property 'Custom' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/DeclarationCouldBeConvertedToProperty/UnderscoreNameField.cs#L5
Non-nullable field '_field' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/DeclarationCouldBeConvertedToProperty/ReadonlyPublicField.cs#L5
Non-nullable field 'field' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/DeclarationCouldBeConvertedToProperty/PublicProperty.cs#L5
Non-nullable property 'Field' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/DeclarationCouldBeConvertedToProperty/PrivateFieldWithoutMethods.cs#L5
Non-nullable field 'test' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Build & Test:
SourceKit.Sample/Analyzers/DeclarationCouldBeConvertedToProperty/OnePublicField.cs#L5
Non-nullable field 'field' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Build & Test:
src/SourceKit/Extensions/TypeSymbolExtensions.cs#L17
Use 'SymbolEqualityComparer' when comparing symbols
|
Build & Test:
src/analyzers/SourceKit.Analyzers.MustBePartial/Analyzers/TypeMustBePartialAnalyzer.cs#L18
Enable analyzer release tracking for the analyzer project containing rule 'SK1000' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)
|
Build & Test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
|
Build & Test
- Add lib or ref assemblies for the netstandard2.0 target framework
|
Build & Test:
src/SourceKit/Extensions/TypeSymbolExtensions.cs#L17
Use 'SymbolEqualityComparer' when comparing symbols
|
Build & Test:
src/analyzers/SourceKit.Analyzers.MustBePartial/Analyzers/TypeMustBePartialAnalyzer.cs#L18
Enable analyzer release tracking for the analyzer project containing rule 'SK1000' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)
|
Build & Test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
|
Build & Test
- Add lib or ref assemblies for the netstandard2.0 target framework
|
Build & Test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
|
Build & Test
- Add lib or ref assemblies for the netstandard2.0 target framework
|