mason-registry
json-schema-spec
mason-registry | json-schema-spec | |
---|---|---|
5 | 30 | |
125 | 3,237 | |
8.8% | 3.4% | |
10.0 | 7.9 | |
3 days ago | 9 days ago | |
JavaScript | ||
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.
json-schema-spec
- Python JSON schema
-
TypeSpec: A New Language for API-Centric Development
Yep and that comes from JSON Schema: https://json-schema.org/
I believe recent versions of OpenAPI are "compatible" with JSON Schema (at least they "wanted to be" last I checked as I was implementing some schema converters).
Even TypeScript is not enough to represent all of JSON Schema! But it gets close (perhaps if you remove validation rules and stuff like that it's a full match).
But even something like Java can represent most of it pretty well, specially since sealed interfaces were added. I know because I've done it :).
- JSON Schema Blog
-
Deploy a simple data storage API with very little code using Amazon API Gateway and DynamoDB
models.tf where I centralized all the Data model that API Gateway uses to perform input and output checks. Those use the JSON-schema specification. GitHub - psantus/serverless.api-gateway-dynamodb-integration.terraform
- Unlocking the frontend – a call for standardizing component APIs pt.2
- JSON Schema
-
How to Automatically Consume RESTful APIs in Your Frontend
In the meantime, we are going to expand our backend with two endpoints: one for fetching data and another one for creating data. Fastify provides out-of-the-box support for API serialization and validation through its schema-based approach built on top of JSON Schema. Through the schema option, we can attach a schema definition to each route.
-
A View on Functional Software Architecture
JSON-schema to define templates for request and response contents.
-
Learn serverless on AWS step-by-step: Strong Types!
The syntax used to define the output is called JSON Schema. It is a standard way to define the structure of a JSON object. If you know zod, the spirit is similar. Based on Swarmion's roadmap, it will be possible to use zod schemas to defined contracts in the future, which will be super cool!
- XML is better than YAML
What are some alternatives?
atlas - Manage your database schema as code
outlines - Structured Text Generation
declarative-schemas
guidance - A guidance language for controlling large language models.
nil - NIx Language server, an incremental analysis assistant for writing in Nix.
uplaybook - A python-centric IT automation system.
purl-spec - A minimal specification for purl aka. a package "mostly universal" URL, join the discussion at https://gitter.im/package-url/Lobby
nix-configs - My Nix{OS} configuration files
language-server-protocol - Defines a common protocol for language servers.
OpenAPI-Specification - The OpenAPI Specification Repository
vscode-postgres - PostgreSQL extension for vscode providing explorer, highlighting, diagnostics, and intellisense
torch-grammar