Titus

It is the items in that list, and could be that section, but the current wording is different than what I’m looking for. That section currently explains what the code...

This issue was particularly about missing unit tests. A comment in the code says something cannot occur, but it can, and should be tested. Some examples: a plugin throwing an...

> testing for a broken configuration file. You mean broken remark or rehype config files? In that case, I do not yet understand the pros and cons of what you...

It might be useful but I’m not sure how much schema validation in the engine/unified-language-server adds compared to: - existing types - existing runtime errors when unexpected values are passed...

- neovim/nvim-lspconfig#1641 shows that the projects that have this problem can solve this problem. In the case of `nvim-lspconfig`, the [remark integration](https://github.com/neovim/nvim-lspconfig/blob/e7df7ecae0b0d2f997ea65e951ddbe98ca3e154b/lua/lspconfig/server_configurations/remark_ls.lua#L14) is different from similar integrations (e.g., stylelint, eslint)....

(Boolean) APIs are typically easier to understand if they default to `false`, and can instead be turned on. Can we come up different option names where the default of `false`...

> For example this is how it’s done by the VS Code extensions for ESLint, Flow, git, Prettier, Stylelint, XML, XO, YAML, and more. I’m okay with checkboxes in VS...

> I miss this feature as an end user using this via both Vim and VSCode. Just like I don’t want to have Prettier format my code in a project...

> Most things in nvim-lspconfig use `root_dir` with `root_pattern` (such as `elm.json`) to detect whether the LS should start. [...] Is it correct that your statement describes how nvim but...

- It is not clear what has to happen in `unified-engine`. I am open to it getting a new option `requireConfig`, which probably has to throw without `rcName`, `packageField`, and...