-
-
Notifications
You must be signed in to change notification settings - Fork 200
Merge monaco-editor-wrapper and monaco-editor-react into monaco-languageclient's npm workspace #600
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
Conversation
e7a2a44
to
ee117e4
Compare
ee117e4
to
0354fe3
Compare
9f51b4f
to
816c4fa
Compare
@CGNonofr I have updated to 2.2.0-next.1 and the font in the command palette is wrong. Should this work without change?
and |
Did I miss changes in the vite configuration? I just checked the your demo config and I didn't see something obvious |
I'm not aware of anything 🤔 The first error looks like the theme service override is not registered The second one is probably due to the webworker extension host not working (the local process extension host is not able to replace worker urls by real urls) |
It is consistently using the wrong font. Did you remove to many global css instructions? Interestingly, codicon is fine. In the past, usually problems originated from there.
I mixed the classical editor mode of the wrapper with the vscode extensions and therefore the themes override was not loaded. My fault.
You have a workaround for that problem in the demo, don't you? Could we generalize that somehow. I need to fix the editor worker issue as well, too. |
There were some removed global style I've added back (with some tweaks to remove properties on the body and so on...) What do you expect and what do you get?
Nop, in the demo, the default extensions run in the worker ext host |
@CGNonofr just tested again with New example Langium Grammar DSL Language Client & Server (Worker) (Chrome on Windows): |
41721dc
to
c2ff580
Compare
Latest force-push using |
4aef2fb
to
2e44d6f
Compare
@CGNonofr I am continuing to merge and update the examples (latest code is not yet pushed). Have you seen this error already? Using the standalone editor here with 2.2.1: |
I am not importing any workbench related things and I guess that should not be needed. |
cba8b08
to
2af7bdd
Compare
should i put this #595 feature on hold until this WIP PR is merged and released ? thx |
Yes, that makes sense. I hope to get this ready finally this week. My own availability will be better again now.
The wrapper allows you already to get access to the editor/model itself. See for example. https://github.com/TypeFox/monaco-languageclient/blob/merge-monaco-edtior-wrapper/packages/wrapper/src/wrapper.ts#L156-L190 This is also put to use in some of the examples. |
@CGNonofr README updates and LICENSE unification are done. CHANGELOGs are next. |
@CGNonofr this is ready for review. Please go ahead. |
There is still a |
A the first one. Nevermind, go ahead |
... or give me a 30 minutes. I can fix the commit message, but need to finish something else first |
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.
didn't spot anything weird but not the easiest PR of my life !
…nify examples - Updated to monaco-vscode-api 2.2.1 - Integrated python wrapper & react wrapper - Integrated json wrapper client web socket example - Converted groovy example to wrapper - Updated versions to 8.0.0-next.0, 4.0.0-next.0 and 3.0.0-next.0
…nstruction of worker - Integrate angular example
- Include build of all verification examples - workerFactory allows to use configuration or worker for the definition
…1. Fix locale loading
… callback is thrown
… monaco-vscode-api 3.1.2, use monaco-editor as dependency designator - Moved some code back from the wrapper to the languageclient as otherwise it can be used standalone - Cleaned enhanced MonacoEnvironment and fixed init bug in new common init function
3118e93
to
b81ff04
Compare
@CGNonofr It's rebased and the first to commits on the branch have been merged. |
Yes, I know and I am sorry for this, but merging this all in one place couldn't be done in small steps. We can iterate from here. |
This PR is now ready for review. A couple of open points should be fixed, but review can start now.
This repository now hosts the following npm packages:
monaco-languagclient
; Next release: https://www.npmjs.com/package/monaco-languageclient/v/8.0.0-next.6vscode-ws-jsopnrpc
; Next release: https://www.npmjs.com/package/vscode-ws-jsonrpc/v/3.3.0-next.6monaco-editor-wrapper
; Next release: https://www.npmjs.com/package/monaco-editor-wrapper/v/4.0.0-next.6@typefox/monaco-editor-react
; Next release: https://www.npmjs.com/package/@typefox/monaco-editor-react/v/3.0.0-next.6monaco-languagclient-examples
; Next release: https://www.npmjs.com/package/monaco-languageclient-examples/v/8.0.0-next.6Important points:
monaco-editor-workers
is no longer needed and is replaced bymonaco-editor-wrapper/workerFactory
that integrates ideas from monaco-vscode-api demo and is fully customizable/over-writeable.monaco-editor-wrapper
or@typefox/monaco-editor-react
. This made reduces the amount of boiler plate code.Left over points required at least required to be implemented before this PR can be merged:
Will close #543