Sergey Chikuyonok
Sergey Chikuyonok
Well, I guess it may work :) However, my only concern here is that there’s a hard dependency for `cssLanguage` and `htmlLanguage`. Also, it may not solve the issue with...
Yes, these languages should be imported somehow into bundle. Might lead to extra size if you have your own syntax highlighter.
Alternatively, I can remove these language bindings and leave a property, as you suggested. I think it’s OK for plugin consumers to manually set language that must be used
Thanks for pinging me up. Just published v0.3.0 which includes `syntax` option to specify document syntax (updated README as well). It also includes most recent Emmet version which also supports...
Yeah, forgot to push it :) should be available already
In v0.2.0, there’s a new `completionBoost` option for that. You can either pass it to `abbreviationTracker()` extension or use `emmetConfig` facet instead, as described in #13
`filter` option is required to properly recalculate completions when user types (e.g. `p` → `p1`). Without this option, CM requires a list of static completions which will be filtered by...
Fixed in v0.2.0: it should properly detect context and won’t provide completions as expected
You should pass syntax highlighting as option: `abbreviation({ preview: { html: yourCustomHighighter } })`
You should pass an extension factory function, which will be invoked when preview widget is created. E.g. ```js import { html } from '@codemirror/lang-html'; abbreviationTracker({ preview: { html: html }...