-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example not working #10
Comments
Better headline |
@Martin-Andersen Currently, it is intentionally by design. See also: #7 (comment) |
This also tripped me up a bit as the errors in Visual Studio are not that great. Would be a great idea to add a note in the sample to the async method exception. |
Just a +1 here. Had an My understanding of ValueTask is it's only of performance improvement if the underlyng async operation completes synchronously...They also have a drastically reduced API surface area (by design). See https://devblogs.microsoft.com/dotnet/understanding-the-whys-whats-and-whens-of-valuetask/ |
Hi everyone, So, the latest preview version of the See also: https://www.nuget.org/packages/Toolbelt.Blazor.HotKeys2/3.3.0-preview.1#releasenotes-body-tab |
In the old version of HotKeys. I wrote this
I tried this in v2, not working
And this not working
Is it because my handler is async?
The text was updated successfully, but these errors were encountered: