The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/variable-substitution@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'DefaultValue' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Type' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Parameters' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Output' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Summary' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Enable analyzer release tracking for the analyzer project containing rule 'BITGEN001' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)

Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'DefaultValue' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Type' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Parameters' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Output' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Summary' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/variable-substitution@v1, Apple-Actions/import-codesign-certs@v1, Apple-Actions/download-provisioning-profiles@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Enable analyzer release tracking for the analyzer project containing rule 'BITGEN001' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The field 'BitSwiper._pagesCount' is never used

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The field 'BitSwiper._pagesCount' is never used

The field 'BitSwiper._currentPage' is never used

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/download-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/variable-substitution@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Enable analyzer release tracking for the analyzer project containing rule 'BITGEN001' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The field 'BitSwiper._pagesCount' is never used

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

Field 'BitNav<TItem>.SelectedItemHasBeenSet' is never assigned to, and will always have its default value false

The field 'BitStack.disableShrink' is never used

The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/variable-substitution@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Enable analyzer release tracking for the analyzer project containing rule 'BITGEN001' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The field 'BitSwiper._pagesCount' is never used

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The field 'BitSwiper._pagesCount' is never used

The field 'BitSwiper._currentPage' is never used

The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/variable-substitution@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

The field 'BitSwiper._currentPage' is never used

The field 'BitStack.disableShrink' is never used

Enable analyzer release tracking for the analyzer project containing rule 'BITGEN001' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

Possible null reference assignment.

Possible null reference assignment.

Possible null reference assignment.

Non-nullable field 'selectedItem' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.