-
Notifications
You must be signed in to change notification settings - Fork 132
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
fix: get container after Workbench is mounted #848
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #848 +/- ##
==========================================
+ Coverage 91.05% 91.06% +0.01%
==========================================
Files 188 188
Lines 6071 6078 +7
Branches 1476 1476
==========================================
+ Hits 5528 5535 +7
Misses 537 537
Partials 6 6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
5f13ec2
to
b89a631
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.
+1
* feat: support onWorkbenchDidMount event * test: unit test for onWorkbenchDidMount event * fix: initWorkspace after workbench did mount * feat: add EmbeddedWorkbench example * fix: rename standalone
Description
Refactor the initial logic of
monacoService
. the initWorkspace method depends on thecontainer
property oflayoutService
, but thecontainer
should be set after theWorkbench
component is mounted.Fixes #846
Changes
layoutService
supports onWorkbenchDidMount event