json-editor
laminar
Our great sponsors
json-editor | laminar | |
---|---|---|
8 | 4 | |
4,220 | 23 | |
2.1% | - | |
9.3 | 0.0 | |
4 days ago | 5 months ago | |
JavaScript | 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.
json-editor
- JSON-editor: generate forms and edit JSON documents using JSON schema
-
What are the real cons of using jenkins?
Combined with the fact that the parameter UI is highly dynamic through plugins(like how the extended choice parameters plugin supports defining complex input forms using json-editor means you can use Jenkins as an interface to run any kind of job that requires almost any type of input.
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
I use JSON schema to generate JSON-editing forms via json-editor: https://github.com/json-editor/json-editor
Then I can use the same schema in the backend to validate the data, both sent in via the form and directly with the application/json content-type. It's a pretty smooth flow, and reduces a lot of redundancy.
-
[TASK] 50$ - App to fill JSON
I have found stuff similar to this, for example json-editor.
-
Repeating form builder
JSON Editor takes a JSON Schema and uses it to generate an HTML form.
-
FormKit — Vue 3 Forms, Supercharged
Some project followed that way like json-editor
-
Suggestions on web interface for inserting values into a YAML document
json-editor is a really easy way to build complex forms. The resulting schema is returned as json which you can just convert to yaml. I use this in Jenkins for complex parameters.
-
Looking for UI for building yaml by schema
https://github.com/json-editor/json-editor was used in the backbone.js version of swagger-ui to generate input forms from json-schema.
laminar
-
Ask HN: Does Anyone Like GraphQL?
The main (and only) criticism I’ve ever heard about graphql in the companies I worked for was that it is very js-oriented all the best libs/frameworks for it are for react frontend / node server mostly.
Backend scala / php devs looked at it with distaste in their eyes, coming up with various reasons why its not a good idea.
And to be fair with tools like openapi / grpc a lot of the benefits of graphql can be replicated.
Even if they are clumsy and fragmented compared to it in my eyes, they still work well enough and keep devs in all camps happy enough, and compromise as they say is “when everyone is equally unhappy”.
Now placed in situations like this I am usually forced to reimplement graphql tooling with the chosen api tech (for example https://github.com/ovotech/laminar) and if me as a single dev could do it, then I’d wager if there was stronger tech leadership, all the other tech tribes could just smooth the edges that they didn’t like for using graphql in their respective languages … but sadly that has not been my experience.
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
I use it extensively in prod. Well the superset that is OpenApi. It enables contract first development where any change to the api is done in the schema fist, and then implemented by the clients/server.
Since we have tooling[0] that validates requests and responses at runtime, the clients can be absolutely sure of what they receive (we through 500 if the server attempts to respond with an undocumented respond) And the server is also sure about the shape of the requests. This allows us to validate everything at compile time too, generating typescript types for both client and server.
And since we have similar tooling regarding our data stores (typescript types for sql queries) most of the time if there is a bug, the code would simply not compile - pretty nifty!
[0] - https://github.com/ovotech/laminar
- SQLBolt – Interactive lessons and exercises to learn SQL
-
Bad TypeScript Habits to Break This Year
If the api has some contract with it OpenApi / Swagger / etc, its surprisingly easy to write a parser that would convert those to typescript types. TS has an awesome use as a library itself where you can write the ast with, and then tell it to convert it to code.
We use it to great effect ourselves, by generating types for axios.
https://github.com/ovotech/laminar/tree/main/packages/lamina...
Now granted, you’re now trusting the api writers with their contract, but if its another team in the org we’ve found it to be warranted.
What are some alternatives?
formkit - Vue Forms ⚡️ Supercharged
pgtyped - pgTyped - Typesafe SQL in TypeScript
adif-json-protobuf - Protocol buffer and JSON schema based on the amateur radio data interchange format (ADIF)
fp-ts - Functional programming in TypeScript
Atom - :atom: The hackable text editor
schema-dts - JSON-LD TypeScript types for Schema.org vocabulary
json-schema - JSON Schema Validation, Annotation, and Bundling. Supports Draft 04, 06, 07, 2019-09, 2020-12, OpenAPI 3.0, and OpenAPI 3.1
alt-schema - Flat JSON Schema specification and basic utility methods
alterschema - Convert between JSON Schema specification versions.
library-recommendations - Evaluating Open Source libraries for particular purposes
tslint - :vertical_traffic_light: An extensible linter for the TypeScript language