feat: add OpenAI-compatbile API support for AI #97
Annotations
11 warnings
Checks
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Checks:
Server/Modules/Users/User.cs#L14
Non-nullable property 'Username' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Checks:
Server/Modules/Items/Services/ItemGenerator.cs#L45
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Checks:
Server/Modules/Items/Services/ItemGenerator.cs#L26
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.
|
Checks:
Server/Components/UI/ItemCard.razor#L40
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.
|
Checks:
Server/Components/UI/ItemCard.razor#L41
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.
|
Checks:
Server/Modules/Items/Models/ItemStatistics.cs#L23
Non-nullable property 'Item' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Checks:
Server/Modules/Users/User.cs#L14
Non-nullable property 'Username' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Checks:
Server/Modules/Items/Services/ItemGenerator.cs#L45
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Checks:
Server/Modules/Items/Services/ItemGenerator.cs#L26
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.
|
Checks:
Server/Components/UI/ItemCard.razor#L40
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.
|