fix: some namespaces #22
HamedSYAnnotations
10 warnings
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Dtos/CreateRepositoryResponseDto.cs#L11
Non-nullable property 'RepositoryName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Dtos/CreateRepositoryCommandDto.cs#L9
Non-nullable property 'DefaultBranch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Dtos/CreateRepositoryCommandDto.cs#L11
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Context/CreateRepositoryRequest.cs#L8
Non-nullable property 'DefaultBranch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Context/CreateRepositoryRequest.cs#L10
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Commands/CreateRepositoryCommandHandler.cs#L15
Non-nullable property 'DefaultBranch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient/Gitea/Repository/CreateRepository/Commands/CreateRepositoryCommandHandler.cs#L17
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-test-deploy:
Mohaymen.GiteaClient.Tests/Gitea/Repository/CreateRepository/Commands/CreateRepositoryCommandHandlerTests.cs#L42
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.
|
|
build-test-deploy:
Mohaymen.GiteaClient.Tests/Gitea/Repository/CreateRepository/Commands/CreateRepositoryCommandHandlerTests.cs#L28
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-test-deploy:
Mohaymen.GiteaClient.Tests/Gitea/Repository/Common/Facade/RepositoryFacadeTests.cs#L39
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.
|