Small fix that fixes map drawing on Server side Blazor. #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! You're right about the async Blazor Server behavior. I'll test it and merge it asap. |
|
Please fix the call to invokeMethodAsync. With this fix we are good to go. |
# Conflicts: # OpenLayers.Blazor.sln
|
Fixed call to use InvokeMethodAsync. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
please find in this PR a small fix that enables the drawing capabilities on Blazor Server hosting model.
Nothing too fancy, just ensuring that the JS interop from the client to the .NET side is done asynchronously, as synchronous calls are not permitted for Blazor Server.
Thanks in advance for creating and maintaining this library & greetings from Germany,
Peter Vrenken