Private feed implementation #156
Merged
Annotations
10 warnings
|
Build:
src/BaGetter.Core/Configuration/BaGetterOptions.cs#L9
XML comment has cref attribute 'ApiKeys' that could not be resolved
|
|
Build:
src/BaGetter.Tencent/TencentStorageOptions.cs#L8
Non-nullable property 'AppId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build:
src/BaGetter.Tencent/TencentStorageOptions.cs#L10
Non-nullable property 'SecretId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build:
src/BaGetter.Tencent/TencentStorageOptions.cs#L12
Non-nullable property 'SecretKey' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build:
src/BaGetter.Tencent/TencentStorageOptions.cs#L14
Non-nullable property 'Region' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build:
src/BaGetter.Tencent/TencentStorageOptions.cs#L16
Non-nullable property 'BucketName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build:
src/BaGetter.Tencent/TencentApplicationExtensions.cs#L27
Possible null reference return.
|
|
Build:
src/BaGetter.Tencent/TencentStorageService.cs#L18
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.
|
|
Build:
src/BaGetter.Tencent/TencentStorageService.cs#L29
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.
|
|
Build:
src/BaGetter.Tencent/TencentStorageService.cs#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.
|
Loading