Got outbound texts, generated from email responses, working in suppor… #612
uncheckederrorAnnotations
9 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@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build:
Messaging/Program.cs#L2039
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:
Messaging/Program.cs#L2053
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:
NumberSearch.Ops/Views/PurchasedPhoneNumbers/NumberOrders.cshtml#L37
Dereference of a possibly null reference.
|
|
build:
NumberSearch.Ops/Views/PurchasedPhoneNumbers/NumberOrders.cshtml#L37
Possible null reference argument for parameter 'input' in 'bool PhoneNumber.TryParse(in string input, out PhoneNumber number)'.
|
|
build:
Messaging/Program.cs#L2039
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:
Messaging/Program.cs#L2053
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:
NumberSearch.Ops/Views/PurchasedPhoneNumbers/NumberOrders.cshtml#L37
Dereference of a possibly null reference.
|
|
build:
NumberSearch.Ops/Views/PurchasedPhoneNumbers/NumberOrders.cshtml#L37
Possible null reference argument for parameter 'input' in 'bool PhoneNumber.TryParse(in string input, out PhoneNumber number)'.
|