Stephen Cleary

I am working on an easier way to work in this scenario, but for now the best solution is to have your _own_ `SignInExecuting` property, set and unset inside `SignInAsync`:...

One part of it is that I'm planning to enhance [`CalculatedProperties`](https://github.com/StephenCleary/Mvvm.CalculatedProperties) so that it can take regular (`NotifyChanged`-style) property changes as input to a calculated expression. Another part of it...

I'm not sure that this would be an improvement. This is the way that all updates work in an MVVM system; you have to read the property after subscribing to...

If you want to call `HandleException` exactly once for each exception, then you should do this: notifyTask = NotifyTask.Create(async => { try { return await methodAsync(); } catch (Exception ex)...

The factory is a specific implementation of the CanExecuteChanged event (not it's logic). The current AsyncCommand class always ties CanExecute to IsExecuting. If you need different logic, you'd need to...

Closing: Too complex to maintain. I've gone down this path with `AsyncCommand` before. In my [article on the subject](https://msdn.microsoft.com/en-us/magazine/dn630647.aspx), I go far enough to support cancellation built-in, and in my...

> I looked at it and didn't immediately see how to use it in connection with AsyncCommand I am planning to write docs specifically for this, since it will definitely...

Being able to specify artifacts by `run_id` *and* `name` would make this common scenario much easier: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ Having to copy/paste the `github-script` everywhere isn't that great of a user experience,...

Do you need it?

That's a great idea, and I should probably do the same for other dependencies, too. On vacation ATM, but I should be able to address this in a couple weeks.