预留了 config,支持在 token 失效之前进行自动刷新 #4
Annotations
8 warnings
build (Release)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build (Release)
No files were found with the provided path: bin/Debug
bin/Release. No artifacts will be uploaded.
|
build (Release):
CSharp-OpenBMCLAPI/Modules/Challenge.cs#L11
Non-nullable field 'challenge' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build (Release):
CSharp-OpenBMCLAPI/Modules/Challenge.cs#L11
Non-nullable field 'challenge' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build (Debug)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build (Debug)
No files were found with the provided path: bin/Debug
bin/Release. No artifacts will be uploaded.
|
build (Debug):
CSharp-OpenBMCLAPI/Modules/Challenge.cs#L11
Non-nullable field 'challenge' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build (Debug):
CSharp-OpenBMCLAPI/Modules/Challenge.cs#L11
Non-nullable field 'challenge' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|