Skip to content

Fixed few bugs in exception handling and file command/query #52

Fixed few bugs in exception handling and file command/query

Fixed few bugs in exception handling and file command/query #52

Triggered via push October 13, 2024 18:56
Status Success
Total duration 4m 12s
Artifacts

develop.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

22 warnings
build-api
Non-nullable property 'Profile' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-api
Non-nullable property 'Files' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-api
Non-nullable property 'Subject' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-api
Non-nullable property 'HtmlBody' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-api
Parameter 'infrastructureSource' is unread.
build-api
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-api
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-api
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-api
Non-nullable property 'Email' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-api
Non-nullable property 'EmailAddress' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-consumer-job
Parameter 'infrastructureSource' is unread.
build-consumer-job
Non-nullable property 'Profile' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-consumer-job
Non-nullable property 'Files' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-consumer-job
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-consumer-job
Non-nullable property 'Subject' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-consumer-job
Non-nullable property 'HtmlBody' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-consumer-job
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-consumer-job
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-consumer-job
Non-nullable property 'Email' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build-consumer-job
Non-nullable property 'EmailAddress' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/