Explicit control over QueueNames , possibility to send message to exp… #78
ppossanziniAnnotations
7 warnings
|
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build:
tests/receiver/Program.cs#L26
'Extensions.ResolveArbitrerCalls(IServiceCollection)' is obsolete: 'use AddRabbitMQRequestManager method instead'
|
|
build:
tests/receiver/handlers/CommandHandler.cs#L42
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:
tests/receiver/handlers/CommandHandler.cs#L47
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:
tests/receiver/Program.cs#L26
'Extensions.ResolveArbitrerCalls(IServiceCollection)' is obsolete: 'use AddRabbitMQRequestManager method instead'
|
|
build:
tests/receiver/handlers/CommandHandler.cs#L42
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:
tests/receiver/handlers/CommandHandler.cs#L47
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.
|