Remco Haszing

I suppose you’re right. :) Perhaps it’s time to officially deprecate this project then.

I happen to be working with Monaco editor inside a Next.js project right now. First, here’s a solution to working with `monaco-editor` without having to use `@monaco-editor/react`: **next.config.js** ```js export...

I’m note entirely sure if this can be resolved in `monaco-yaml` or if it needs to be resolved upstream in `yaml-language-server`. This needs some investigation. I also ran into this...

I’m going to delay this until `monaco-editor` 0.34.0 is released, because that release will include the `onEnterRules` that were included in the `monaco-yaml` basic language support.

I’m delaying this further. CI is broken for `monaco-editor` 0.34.0 upstream and I don’t trust that release for now.

I can think of 2 solutions: 1. Allow to specify a severity override to the `monaco-yaml` options. 2. Add a marker data interceptor function to process them before sending the...

May I ask why you need this feature? I can also imagine YAML syntax errors should be errors, but schema violations warnings. I think that would conflict with your feature...

I think `yaml-language-server` simply doesn’t do validation if the document is empty. I think this is indended behaviour. This decision isn’t made by `monaco-yaml`. If the type is incorrect, it...

> Could an upgrade to yaml-language-server v1.0 fix this (I saw that you replaced nodeca/js-yaml with eemeli/yaml over there)? This isn’t fixed by the upgrade to yaml-language-server 1.0. (See #126)...

I would like to see tests too, although I’m not sure if unittests are the right way to test this. I think this would require a lot of stubbing which...