custom-elements-manifest
awesome-jsonschema
custom-elements-manifest | awesome-jsonschema | |
---|---|---|
4 | 70 | |
335 | 101 | |
2.1% | 4.0% | |
1.5 | 5.3 | |
11 days ago | 8 months ago | |
TypeScript | Handlebars | |
BSD 3-clause "New" or "Revised" License | Creative Commons Zero v1.0 Universal |
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.
custom-elements-manifest
-
The Block Protocol
The Web Components Community Group is developing such a format to describe the types of components here: https://github.com/webcomponents/custom-elements-manifest
People have already built tools that generate wrappers based on it.
-
Reactifying Custom Elements using a Custom Elements Manifest
TL;DR: A Custom Elements Manifest is a JSON file that contains all metadata about the custom elements in your project. You can read all about it here.
-
Introducing: Custom Elements Manifest
Custom Elements Manifest is a file format that describes the custom elements in your project. This format will allow tooling and IDEs to give rich information about the custom elements in a given project. A custom-elements.json contains metadata about the custom elements in your project; their properties, methods, attributes, inheritance, slots, CSS Shadow Parts, CSS custom properties, and a modules exports. If you're interested in following the specification of the schema, or contributing to it, you can find the repository here: webcomponents/custom-elements-manifest.
awesome-jsonschema
- YAML or JSON files that are typed?
- Parse, Don't Validate (2019)
-
The Last Breaking Change | JSON Schema Blog
Truth. Zod is comparable to JSON Schema plus AJV, and it doesn't compare well at all. Your Zod code is all locked inside TypeScript so not only can it not be shared to any other language in your stack but it also cannot be serialized, which introduces many limitations. You also miss out on all the JSON Schema ecosystem tooling. (1, 2) For example the intellisense you get in VS Code for config files is powered by JSON Schema and schemastore.
The very first line of text below the header on the json-schema.org homepage is:
-
How to use FastAPI for microservices in Python
The framework's official website mentions a number of pros of FastAPI. In my opinion, the most useful features from a microservice perspective are: the simplicity of code (easy to use and avoid boilerplate), high operational capacity thanks to Starlette and Pydantic and compatibility with industry standards - OpenAPI and JSON Schema.
-
How to handle forms in a good way?
I've used Felte to reduce form boilerplate. Felte supports several different validation libraries like Zod. I actually used a custom validation function with ajv (which uses JSON schema).
-
A Brief Defense of XML
(There is already a JSON Schema definition at https://json-schema.org/)
Like you said - standard XML isn't terrible. Adding on an XSD isn't terrible, because now you can enforce structure and datatypes on files provided by outside parties. Creating an XSLT is much more of a mental challenge, and probably should be left to tools to define.
Anything beyond those technologies is someone polishing up their resume.
-
On the seventh day of Enhancing: Forms
While the aws-sdk is being installed to simulate DynamoDB locally, let me explain a few things about this command. First Comment will be the name of the model the scaffold creates. This model will be codified under app/models/schemas/comment.mjs as a JSON Schema object. Each of the parameters after Comment will be split into a property name and type (e.g. property name “subject”, property type “string”). This JSON Schema document will be used to validate the form data both on the client and server sides.
-
Server Sent UI Schema Driven UIs
What you are looking is called Json-schema. Have a look at the implementations page, which will give you an idea of what you can do with json-schema, which also includes UI rendering.
- Tool to document Firestore 'schema'
What are some alternatives?
catalyst - Catalyst is a set of patterns and techniques for developing components within a complex application.
zod - TypeScript-first schema validation with static type inference
open-wc - Open Web Components: guides, tools and libraries for developing web components.
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
api-viewer-element - API documentation and live playground for Web Components. Based on Custom Elements Manifest format
JSON-Schema Faker - JSON-Schema + fake data generators
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
fastify-swagger - Swagger documentation generator for Fastify
eleventy 🕚⚡️ - A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
pydantic - Data validation using Python type hints
custom-elements-manifest
Superstruct - A simple and composable way to validate data in JavaScript (and TypeScript).