monaco `0.35.0` support about emmet-monaco-es HOT 6 CLOSED

I'll fix it next Monday :)

from emmet-monaco-es.

It seems the dist code of [email protected] mangled private and protected properties of class which was used inside this project microsoft/vscode-discussions#257 microsoft/vscode#166126.
I can somehow find the mangled property but it not seems promising.

from emmet-monaco-es.

v5.2.0 was release by switching to mangled property name, could be broken in next monaco-editor release

from emmet-monaco-es.

@troy351 – does monaco not expose enough documented APIs to implement emmet without access to private/protected members?

from emmet-monaco-es.

microsoft/vscode-discussions#257 (comment)

we do have source map information for mangled properties and anyone can use those to reverse map the non-mangled names. Fundamentally, patching VS Code is still possible it just got harder because names are shortened (for the reasons outlined above). Generally, extension relying on patching internals are tolerated but not supported. Doing so would put us into a position where absolutely no change is possible anymore. Future engineering work, like the upcoming AMD to ESM migration, can cause a similar swirl and we will not pause them.

from emmet-monaco-es.

In order to trigger emmet at the correct location, token information was needed. And internal api was used to get token in a performant way. Public api can only tokenize whole file which is very slow in large files.

from emmet-monaco-es.