refactor(devtools): disable unsupported features - #60585
Conversation
32c78f3 to
4be0224
Compare
23a7a37 to
2b0b8bc
Compare
|
@dgp1130, the PR is ready. All new changes are in the fixup commit. I had to do some code restructuring – mainly extracting |
dgp1130
left a comment
There was a problem hiding this comment.
Left some minor suggestions, but overall I think this looks great! Thanks for pushing on this.
There was a problem hiding this comment.
Question: How does DevTools behave if there are multiple roots and one is Angular and another is not? Could we enable these tabs as long as any one app is Angular? Would the functionality in those tabs even work?
There was a problem hiding this comment.
I was considering that for some time as well but since we don't formally support multiple applications yet and I am not entirely sure how the app will react, I decided to play it on the safe side and disable the features altogether. I can do a more thorough check sometime next week.
There was a problem hiding this comment.
Agreed it's untreaded ground, I'm mainly curious to how well DevTools reacts to multiple roots from the same application. I feel like that should work, but I haven't tried it.
I'm ok to be more restrictive here and we can open it up when we get to proper multi-app support.
Prepare the app for Wiz & ACX and handle unsupported features by disabling their respective UI.
2b0b8bc to
92e8a9d
Compare
AleksanderBodurri
left a comment
There was a problem hiding this comment.
Thanks for this @hawkgs 🙏
|
Switching to |
|
This PR was merged into the repository by commit cebb9d2. The changes were merged into the following branches: main |

PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Prepare the app for Wiz & ACX and handle unsupported features by disabling their respective UI.
Does this PR introduce a breaking change?