nestedtext
typebox
nestedtext | typebox | |
---|---|---|
8 | 57 | |
335 | 4,265 | |
- | - | |
7.9 | 8.7 | |
7 days ago | 5 days ago | |
Python | TypeScript | |
MIT License | 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.
nestedtext
-
The yaml document from hell
As /u/astatine said, an excellent but under-recognized alternative syntax for configuration files is NestedText, where everything is a string unless the ingesting code says otherwise, and there is no escaping needed ever.
-
Yaml: First Class Citizen?
I don't know what traits from markdown you'd hope for, but for a relatively obscure but technically excellent format, you can check out NestedText.
-
A Nigthtmare called YML
I recently came to appreciate and favor an alternative format called NestedText. Like YAML, indentation is used for structure, so like YAML, you may hate it.
-
nt2: a CLI converter between NestedText and JSON, YAML, or TOML
I recently discovered NestedText, and really appreciate the design. To me, it hits the nail on the head where projects like strictyaml and hjson come very close.
-
YAML: It's Time to Move On
I'm glad to see people experimenting with alternative document/object representations, but this one might be a hard sell: based on the README[1], it only has Python, Zig and Janet implementations so far. One of the nice things about YAML (and JSON, TOML, etc.) is that they have decently mature C, C++, or Rust libraries that other languages bind to.
[1]: https://github.com/KenKundert/nestedtext
-
My two favorite things share the same love as me for YAML!
NestedText
-
Json alternatives
NestedText was left out. Has the feel of YaML, without all the complexity and user traps.
- KenKundert/nestedtext ... Human Readable and Writable Data Interchange Format
typebox
-
Popular Libraries For Building Type-safe Web Application APIs
The documentation can be found here.
-
I write HTTP services in Go after 13 years (Mat Ryer, 2024)
So far I like the commonly used approach in the Typescript community best:
1. Create your Schema using https://zod.dev or https://github.com/sinclairzx81/typebox
2. Generate your Types from the schema. It's very simple to create partial or composite types, e.g. UpdateModel, InsertModels, Arrays of them, etc.
3. Most modern Frameworks have first class support for validation, like is a great example Fastify (with typebox). Just reuse your schema definition.
That is very easy, obvious and effective.
- Where DRY Applies
-
Has anybody used Typia library?
There's a ton of schema validators out there and most devs have their personal favorite. Mine was zod and is now typebox + ajv.
- I'm looking to use my openapi spec to dyanamically create types
-
How can I generate typescript types?
If you're willing to document your API with an OpenAPI schema, then it should be possible to generate TypeScript types based on the OpenAPI schema with something like openapi-typescript. Also, Typebox can generate JSON schemas, maybe it can be used to generate something that the front-end can also use?
-
[AskTS] What do you think will be the future of runtime type checking?
Well, I do provide extensibility for those bullet points you've listed to varying degrees (both schema and type representation), as well as offering a reference implementation for expressing a entirely different schema specification under the type system (specifically RFC8927 / JSON Type Definition). Reference implementation here. As for JSDoc, It's supported in code hints.
- TypeBox: Runtime Type System Built on Industry Standards
- TypeBox: A Type System for JavaScript built on Industry Standard Specifications
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
In setting out to build this service, we wanted to use gRPC for its APIs. We’ve been reaching for REST when building APIs so far, primarily out of necessity, i.e., our public APIs needed auto-generated client SDKs and docs for developers working with them. We built those APIs with Fastify and Typebox but felt burned by a code-first approach to generating an OpenAPI spec. I’ll spare you the details and save that experience/learning for another article. Suffice it to say we love gRPC’s schema-first approach. This blog post summarizes our feelings well
What are some alternatives?
strictyaml - Type-safe YAML parser and validator.
zod - TypeScript-first schema validation with static type inference
sublime-json5 - JSON5 support for Sublime Text
zod-to-json-schema - Converts Zod schemas to Json schemas
yaml-reference-parser
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
skycfg - Skycfg is an extension library for the Starlark language that adds support for constructing Protocol Buffer messages.
class-validator - Decorator-based property validation for classes.
dhall-lang - Maintainable configuration files
openapi-typescript-validator - Generate typescript with ajv validation based on openapi schemas
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
ts-json-schema-generator - Generate JSON schema from your Typescript sources