Update to support another implementation with Blazor where messages d… #1
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
…oes not include *blazor?id* in the path.
|
This sounds like a good update, I am going to fork the PR instead of the main project now! |
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! First of all thanks for your work with this extension. In case it helps, here are some changes I made first to be able to compile the app with the latest version of the montoya-api. Then I made some other changes to support a Blazor APP that I recently ran into. This other app does not follow the same approach of including the _blazor?id as part query string in each request. But instead it included the SignalR header in each request for example. Therefore, I used that to recognize the messages and enable the parsing.
Thanks!