Proof of Concept Chrome Extension #2
Conversation
This file contains hidden or 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
Creates a Blazor panel in Chrome Developer tools. Clicking the extension (Blazor Icon) in the Chrome toolbar provides an informational message to the user about how to access the Blazor panel.
Author
|
Just noticed I set the version to 1.0 in the manifest, it should probably be changed to 0.0.1 😄 |
Owner
|
Love it. This is exactly what I had imagined for the project. Just getting back to it now and will look into this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Creates a Blazor panel in Chrome Developer tools. Clicking the extension (Blazor Icon) in the Chrome toolbar provides an informational message to the user about how to access the Blazor panel.
Instructions for loading the unpacked extension into Chrome
https://developer.chrome.com/docs/extensions/mv3/getstarted/development-basics/#load-unpacked
If this PR is accepted, I will create an issue with a task list for tracking initial development of core functionality.
I've been building a custom version of blazor.webassembly.js from here https://github.com/dotnet/aspnetcore/tree/main/src/Components/Web.JS trying to pinpoint where information about currently rendered components (App, Index, Counter, SurveyPrompt, etc) can be extracted on the client side. If and when these features are identified, this extension should be able to interface with the web page where Chrome Dev Tools is opened and display that information in a user-friendly way.