-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
refactor(core): workbench #7355
base: canary
Are you sure you want to change the base?
Conversation
Your org has enabled the Graphite merge queue for merging into canaryAdd the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 6447019. 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. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## canary #7355 +/- ##
=======================================
Coverage 58.23% 58.24%
=======================================
Files 856 853 -3
Lines 37735 37746 +11
Branches 4087 4086 -1
=======================================
+ Hits 21976 21984 +8
- Misses 15466 15469 +3
Partials 293 293
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
9501dec
to
7a962af
Compare
391b08e
to
c0d17c4
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.
can you update the description on the purpose of changes?
import { createNavigableHistory } from '../../../utils/navigable-history'; | ||
import type { ViewScope } from '../scopes/view'; | ||
|
||
export class View extends Entity { | ||
id = this.scope.props.id; | ||
|
||
sidebarTabs$ = new LiveData<string[]>([]); |
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.
🤔 Why not keep Sidebar
entity but manage in view directly?
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.
I deleted the sidebar, and the sidebar is now managed by the view
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.
Yes, I meant that is it more intuitive to maintain a Sidebar
entity for the logic of the sidebar, as view.sidebar
?
Simplified the logic of the sidebar, which was a bit over-designed before. And now that the sidebar is included in the workbench, their states can also be saved and persisted together. |
da08b91
to
6ae500b
Compare
6ae500b
to
6447019
Compare
Merge the right sidebar logic into the workbench. this can simplify our logic.
Previously we had 3 modules
Now everything is managed in Workbench.
Behavioral changes
The sidebar button is always visible and can be opened at any time.
If there is no content to display, will be
No Selection
Elements in the sidebar can now be defined as
unmountOnInactive=false
. Inactive sidebars are marked withdisplay: none
but not unmount, so theChatPanel
can always remain in the DOM and user input will be retained even if the sidebar is closed.