Describe the solution you'd like
When using the ReactiveCommand attribute, it would be nice if the generated command stripped out the Async suffix from the command name when using methods that end with Async.
For example.
[ReactiveCommand]
private Task InitializeAsync()
{
...
}
Currently, this would result in a command named InitializeAsyncCommand. The desired functionality would be to have a command named InitializeCommand generated.
The MVVM Toolkit does something similar with this implementation.
Describe alternatives you've considered
The workaround right now is to just omit the Async suffix on methods that return tasks. This can vary from team to team as to whether they add this suffix.
Describe the solution you'd like
When using the
ReactiveCommandattribute, it would be nice if the generated command stripped out the Async suffix from the command name when using methods that end with Async.For example.
Currently, this would result in a command named
InitializeAsyncCommand. The desired functionality would be to have a command namedInitializeCommandgenerated.The MVVM Toolkit does something similar with this implementation.
Describe alternatives you've considered
The workaround right now is to just omit the
Asyncsuffix on methods that return tasks. This can vary from team to team as to whether they add this suffix.