ReactiveCommand with running scheduler (not output scheduler)

[Micha-kun]

This is primarily related to Task Commands, but maybe other commands could benefit from this. When I'm creating Task Commands, because I try to run on background thread always, I'm "polluting" every command with Task.Run envelopes around my real code. It would be interesting if ReactiveCommand attribute via Source Generators could generate that envelope to force the running of the code inside a Task.Run (using, for example, ForceTaskRun = true, by default false) or maybe better, a property like RunningScheduler that runs all the command code in that scheduler (by default null or RxApp.MainThreadScheduler).

What do you think?

[glennawatson]

The second option is slightly harder unless it's a enum of common schedulers or something, or maybe a type of a scheduler.

[Micha-kun]

I was thinking doing it like with OutputScheduler property:

[ReactiveCommand(OutputScheduler = "RxApp.MainThreadScheduler")]

[ReactiveCommand(OutputScheduler = nameof(_customScheduler))]

[glennawatson]

Yeah could probably work. Be a bit of analyzer work just to validate I guess but seems doable.