Skip to content

Refactor methods and update layout options #215

Refactor methods and update layout options

Refactor methods and update layout options #215

Triggered via pull request November 14, 2024 22:14
Status Success
Total duration 15m 7s
Artifacts

codeql-analysis.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Analyse: src/Caliburn.Micro.Core.Tests/ConductorWithCollectionOneActiveTests.cs#L42
Member 'ConductorWithCollectionOneActiveTests.ActivateScreen.OnActivateAsync(CancellationToken)' overrides obsolete member 'Screen.OnActivateAsync(CancellationToken)'. Add the Obsolete attribute to 'ConductorWithCollectionOneActiveTests.ActivateScreen.OnActivateAsync(CancellationToken)'.
Analyse: src/Caliburn.Micro.Core.Tests/ScreenExtentionTests.cs#L104
Member 'ConductWithTests.StateScreen.OnActivateAsync(CancellationToken)' overrides obsolete member 'Screen.OnActivateAsync(CancellationToken)'. Add the Obsolete attribute to 'ConductWithTests.StateScreen.OnActivateAsync(CancellationToken)'.
Analyse: src/Caliburn.Micro.Core.Tests/ScreenExtentionTests.cs#L111
'Screen.OnActivateAsync(CancellationToken)' is obsolete: 'Override OnActivatedAsync'
Analyse: src/Caliburn.Micro.Platform/Platforms/Maui/Android/ActivityLifecycleCallbackHandler.cs#L112
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyse: src/Caliburn.Micro.Platform/Platforms/Maui/Android/ActivityLifecycleCallbackHandler.cs#L147
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.