-
Notifications
You must be signed in to change notification settings - Fork 33
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
Proposal: DevTools #374
Comments
Input from @yurist38 would be highly appreciated since he already has experience with such tools. |
@fahad19 Thanks for mentioning me! If you have any thoughts (or even better a mockup) about how that extension should look like, that would help developers to start. And of course, if someone will be interested we could organize some knowledge transfer session. |
@yurist38: I will update you soon here. |
I am currently thinking of something like this:
|
if anyone is interested, ping me right away. I will set up the repo and add you there so that it can be started. |
@fahad19 Since the initiative for Frint DevTools is already approved could you please create a repo. |
@yurist38: done. you are admin of this repo now: https://github.com/frintjs/frint-devtools |
(Intended to be created in a separate repository)
Currently
When we try to debug a regular Frint app (involving root and children), we tend to investigate it by logging
window.app
in the Chrome DevTools console.Use cases involve:
At the moment, to do all of that, developers need to have knowledge of internal APIs of Frint to move forward with debugging.
Proposal
A Developer Tools extension, can be targeted for Chrome only for now, where developers get to see the current situation of Root and Child Apps. The common use cases listed above should be handled by this extension at least.
By default, it can take
window.app
as a source. But the extension should be configurable by the developer to use any other variable name.Example for React: https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en
Source: https://github.com/facebook/react-devtools
The text was updated successfully, but these errors were encountered: