postgres-ast-deparser
mason-registry
| postgres-ast-deparser | mason-registry | |
|---|---|---|
| 1 | 5 | |
| 36 | 125 | |
| - | 8.8% | |
| 10.0 | 10.0 | |
| almost 2 years ago | 4 days ago | |
| PLpgSQL | ||
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postgres-ast-deparser
-
Show HN: Postgres Language Server
actually I forgot to mention this one to Lukas in all the chaos leading up to our Launch Week. I will do it now
we talked in the past about using their library to extend some of Dan Lynch's work (https://github.com/pyramation/postgres-ast-deparser) to create a sort of "postgres package registry" with dynamic DDL introspection. No progress on that one yet, but I'm hopeful that we'll find the bandwidth for it one day.
mason-registry
-
Show HN: Postgres Language Server
Can you try to get it added to Mason so people don't have to try and do a custom install?
https://github.com/mason-org/mason-registry/
- saltstack development in neovim
-
Astronvim Python DAP not starting
There was a bug in the new mason registry that I fixed this morning: https://github.com/mason-org/mason-registry/pull/1056
-
PSA: Changes to the mason.nvim registry
Hello! This is a PSA for people who use mason.nvim (tl;dr at the bottom). Going forward the core registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This decouples the infrastructure in such a way that the Lua plugin becomes a standalone client that can be hooked into more registries than just the core one, as well as more easily be subject to versioning (mason.nvim currently doesn't version itself due to the fact that packages are bundled with it, which complicates things). This decoupling also lowers the barrier of entry for additional maintainers who can solely focus on the registry, without having to learn the internals of the plugin (more info will come soon if you're interested in possibly helping maintain the core registry).
Going forward the core mason.nvim package registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This will be a fully seamless migration so you shouldn't notice anything and there is no action required. Refer to the full announcement post for more information.
What are some alternatives?
language-tools - ⚡ High-performance Vue language tooling based-on Volar.js
atlas - Manage your database schema as code
declarative-schemas
Visual Studio Code - Visual Studio Code
nil - NIx Language server, an incremental analysis assistant for writing in Nix.
libpg_query - C library for accessing the PostgreSQL parser outside of the server environment
purl-spec - A minimal specification for purl aka. a package "mostly universal" URL, join the discussion at https://gitter.im/package-url/Lobby
vetur - Vue tooling for VS Code.
language-server-protocol - Defines a common protocol for language servers.
vscode-postgres - PostgreSQL extension for vscode providing explorer, highlighting, diagnostics, and intellisense