Nullability of reference types in return type of 'string? HelpCommand.Identifier.get' doesn't match implicitly implemented member 'string ICommand.Identifier.get' (possibly because of nullability attributes).

Nullability of reference types in return type of 'string? RootCommand.Identifier.get' doesn't match implicitly implemented member 'string ICommand.Identifier.get' (possibly because of nullability attributes).

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.

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.

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.

Nullability of reference types in return type of 'string? HelpCommand.Identifier.get' doesn't match implicitly implemented member 'string ICommand.Identifier.get' (possibly because of nullability attributes).

Nullability of reference types in return type of 'string? RootCommand.Identifier.get' doesn't match implicitly implemented member 'string ICommand.Identifier.get' (possibly because of nullability attributes).

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.

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.