-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(graph): decouple graph client from nx.dev <Fence> component #21186
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 272b46f. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
c26c920
to
1ed3cc7
Compare
1ed3cc7
to
985984a
Compare
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.
LGTM! Some styling changes should be made imo but the scope of this PR is just clean-up so I'd merge it like this for now.
985984a
to
a0198d5
Compare
a0198d5
to
272b46f
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This PR adds a new component for rendering JSON blocks inside graph client.
Changes
@nx/shared-ui-fence
to@nx/nx-dev/ui-fence
@nx/shared-ui-selector
and inlineSelector
component in@nx/nx-dev/ui-fence
lib since it's only used there as an internal component@nx/graph/ui-code-block
lib to render JSON blocks for the project detail viewpreact/debug
to graph client so we can use devtools