AllowsMultipleExecutions missing from AsyncRelayCommand

[Orgbrat]

In Maui the maintainers are saying if you use MVVM then you should use CommunityToolkit.Mvvm by Microsoft.Toolkit which is perfectly fine. It does have everything that you would need from Xamarin.Community.Toolkit ObjectModel. But the CommunityToolkit.Mvvm AsyncRelayCommand does not have a way to stop multiple executions like the old Xamarin.Community.Toolkit did. And that was really handy because almost 100% of my calls into the Xamarin.Community.Toolkit AsyncCommand had allowsMultipleExecutions set to false so the user could not double click buttons and stuff. I really do miss that in the AsyncRelayCommand in the CommunityToolkit.Mvvm. Since the new CommunityToolkit.Maui will no longer have the AysncCommand and we are told we should use CommunityToolkit.Mvvm I thought we would start having a discussion about maybe adding it to this toolkit. Maybe we can see what other people have to say about this new feature request?

Steve Graddy

[Sergio0694]

Posting this the same answer from the orginal discussion in the MAUI Community Toolkit discussion (here) for future reference:

Hi @Orgbrat, this is a perfectly reasonable feature request and in fact it was already on my to-do list. We had to pause work for a bit for the 7.1 release of the Windows Community Toolkit, and then to take the time to split off all the .NET packages into the new .NET Community Toolkit (which will have its own separate repo), so we didn't want to open any new PRs for the .NET packages there that might potentially "get stuck" during this transition. I already have this feature implemented and prototyped locally, and I plan to open a PR to merge this into the MVVM Toolkit as one of the first new features there. Once that's in, you'll be able to grab a preview package from our CI and start using it into your application. The API shape is pretty much the same as you suggested: there will be new constructor overloads taking a bool parameter to indicate whether the command is allowed to execute multiple invocations concurrently, and setting this will affect how CanExecute will behave (and consequently, how Execute will behave as well). Hope this helps! 😄