laminar
alterschema
laminar | alterschema | |
---|---|---|
4 | 2 | |
23 | 61 | |
- | - | |
0.0 | 7.0 | |
6 months ago | 9 days ago | |
TypeScript | JavaScript | |
GNU General Public License v3.0 or later | 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.
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.
alterschema
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
A project exists which does this, and the team even support its development: https://github.com/sourcemeta/alterschema
Personally, I'd like to see it become officially supported. We have work to do!
What are some alternatives?
pgtyped - pgTyped - Typesafe SQL in TypeScript
raml-spec - RAML Specification
fp-ts - Functional programming in TypeScript
schema-dts - JSON-LD TypeScript types for Schema.org vocabulary
open-kun - Open source Al-Kun
alt-schema - Flat JSON Schema specification and basic utility methods
OpenMetadata - Open Standard for Metadata. A Single place to Discover, Collaborate and Get your data right.
tslint - :vertical_traffic_light: An extensible linter for the TypeScript language
dynamic_dns - A Dynamic DNS Widget
zod - TypeScript-first schema validation with static type inference