⚰️ Remove references from BlazorDb #26
Annotations
12 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3, JamesIves/github-pages-deploy-action@3.7.1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: JamesIves/github-pages-deploy-action@3.7.1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Publish .NET Core Project
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
Publish .NET Core Project:
Timely/Services/Data/ShiftManager.cs#L67
Possible null reference argument for parameter 'source' in 'IOrderedEnumerable<Shift> Enumerable.OrderBy<Shift, int>(IEnumerable<Shift> source, Func<Shift, int> keySelector)'.
|
|
Publish .NET Core Project:
Timely/Components/TimeRecord.razor#L12
Nullable value type may be null.
|
|
Publish .NET Core Project:
Timely/Components/TimeRecord.razor#L12
Nullable value type may be null.
|
|
Publish .NET Core Project:
Timely/Components/TimeRecord.razor#L15
Nullable value type may be null.
|
|
Publish .NET Core Project:
Timely/Components/TimeRecord.razor#L19
Nullable value type may be null.
|
|
Publish .NET Core Project:
Timely/Components/TimeRecord.razor#L35
Non-nullable property 'Shift' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish .NET Core Project:
Timely/Pages/Home.razor#L15
Dereference of a possibly null reference.
|
|
Publish .NET Core Project:
Timely/Pages/Home.razor#L15
Nullable value type may be null.
|
|
Publish .NET Core Project:
Timely/Pages/Home.razor#L118
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Loading