feature: update schema source #54
Labels
Comments
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
folke
added a commit
that referenced
this issue
Jul 6, 2024
This fixes a few issues relating to the CI json schema generation. - befcc1f fixes #60, and also fixes several other servers that previously had an empty `properties` in the schema. This happened because `c.properties` is a table, which means `vim.list_extend` doesn't do anything. `properties` should also always be an object and not an array, so `vim.empty_dict()` is now being used to prevent outputting `[]` when `properties` is empty. - 84e19f4 embeds `index.json` rather than downloading it every time. As mentioned in #54, the gist is no longer maintained, so there's no reason to download it anymore. In the future this should probably be [sourced from elsewhere](https://gist.github.com/williamboman/a01c3ce1884d4b57cc93422e7eae7702?permalink_comment_id=4689512). - 2a911fd fixes the URL for Volar. - 6dfd503 is just me running the build step locally. If I shouldn't have done this I'm happy to revert it. Fixes #52 Fixes #60 Co-authored-by: Folke Lemaitre <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Did you check the docs?
Is your feature request related to a problem? Please describe.
The schema gist that Neoconf is using is no longer maintained, and some LSPs are already outdated (for example, Volar), and build steps no longer generate JSON files.
Describe the solution you'd like
Perhaps we should consider switching sources, as suggested by the original gist author? Link
Describe alternatives you've considered
Maintaining the old gist seems unlikely, as it would require a significant amount of effort
Additional context
No response
The text was updated successfully, but these errors were encountered: