-
Notifications
You must be signed in to change notification settings - Fork 140
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
New Object Inspector UI (architecture investigation) #7235
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
packages/bvaughn-architecture-demo/components/inspector/values/FunctionRenderer.tsx
Show resolved
Hide resolved
✅ QA Wolf - Deploy PRHello here: 8 tests ran, see details here. ✅ 8 passed |
Obviously there's a lot of code here :) Skimmed through it, and it seems pretty legible, well-structured, and well-commented. Really, my main question is: what's a feasible path to adding this to the existing codebase? |
export interface GetTestsRun_node_Workspace_testRuns_recordings_edges_node { | ||
__typename: "Recording"; | ||
uuid: any; | ||
duration: number | null; | ||
createdAt: any; | ||
metadata: any | null; | ||
comments: GetTestsRun_node_Workspace_testRuns_recordings_edges_node_comments[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wish I knew why I had to update this file to make our CI type check happy. I didn't touch anything related to this.
Thanks Mark! After some discussion over VC, I'm going to go ahead and land this change set, and then iterate on it some more with a follow up PR. |
This PR adds a new Object Inspector. Key concepts include:
Suspense
.ValueFront
.Offscreen
API used to remember state (e.g. collapsed/expanded) in conditionally-rendered children.Loom walk through of the architecture:
https://www.loom.com/share/69b18fb36bfb4ab6b70a2bda49afa499
To test the new component:
cd packages/bvaughn-architecture-demo && npm run dev
)FE-322