graphql-lodash
graphql-spec
| graphql-lodash | graphql-spec | |
|---|---|---|
| 1 | 37 | |
| 1,222 | 14,230 | |
| 0.0% | 0.2% | |
| 0.0 | 5.8 | |
| almost 2 years ago | 29 days ago | |
| TypeScript | Shell | |
| MIT License | - |
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.
graphql-lodash
-
Aliasing a nested field as a parent field
Otherwise, if using a JS server you can possibly use GraphQL Lodash, or otherwise you can do it with a custom directive. But be aware that this way you'll be changing the shape of the response to not match the shape of the query anymore, which goes against the GraphQL spec. (This is no problem as long as you know what you're doing.)
graphql-spec
-
Show HN: REST Alternative to GraphQL and tRPC
GraphQL's first draft release was 8 years ago. [1]
It's first non-draft release was 5 years ago. [2]
It's first release under a community foundation was 2 years ago. [3]
[1] https://spec.graphql.org/July2015/
[2] https://github.com/graphql/graphql-spec/releases/tag/June201...
[3] https://github.com/graphql/graphql-spec/releases/tag/October...
-
Intro to PostGraphile V5 (Part 3): Introspection and Abstraction
I'm a big believer in GraphQL (in fact, at time of writing I'm #2 contributor to the GraphQL spec itself) so it pains me that a tool I built doesn't always have easy ways to achieve the "versionless schema" design that GraphQL encourages when it comes to making significant breaking changes to your underlying database tables. (Personally, I think you should aim for your database schema itself to be versionless, but this is not always possible.) Of course you can build your PostGraphile schema over views instead of tables, but views have their own problems that I won't go into here…
-
Migrating Netflix to GraphQL Safely
I created a proposal for Map type but didn’t make it through.
https://github.com/graphql/graphql-spec/pull/888
The issue with GraphQL is it tries to appease too many masters.
Similar to jsx. The language isn’t evolving.
The good thing is the spec is (almost) frozen, so there’s many implementations, the bad is it can encompass the flexibility of json schema can do.
-
GraphQL Live Queries with live directive
Longer thread - Subscriptions RFC: Are Subscriptions and Live Queries the same thing?
https://github.com/graphql/graphql-spec/issues/284
-
Ask HN: Tutorials Written with Heavy Dependencies
You’ve probably figured it out by now, but for others who may be in a similar position; GraphQL is a specification (with various implementations) and you can read up on the spec here: https://spec.graphql.org/
-
GraphQL object schemas - how to represent (and query?) Graph (hierarchical objects) in GraphQL?
If you're asking whether GraphQL supports anonymous objects that can be arbitrarily nested then no, it doesn't.
- Union for an input to a mutation arg
-
Thanks graphql, I hate it.
show this feature request some love https://github.com/graphql/graphql-spec/issues/174
-
Deprecation Notice: GraphQL for Packages
* Performance: It's just hard to track down what makes an operation slow. The waterfall nature of resolvers is a big contributor
[1] https://github.com/graphql/graphql-spec/issues/488
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::note GraphQL Union is available for Types only, not for Inputs. However, the oneOf directive will bridge the gap in the future.
What are some alternatives?
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
apollo-server - 🌍  Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
graphql-ws - Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client.
Neo4j - Graphs for Everyone
graphql-shield - 🛡 A GraphQL tool to ease the creation of permission layer.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
lit-element - LEGACY REPO. This repository is for maintenance of the legacy LitElement library. The LitElement base class is now part of the Lit library, which is developed in the lit monorepo.
react-relay - Relay is a JavaScript framework for building data-driven React applications.
dgraph - The high-performance database for modern applications
graphql-js - A reference implementation of GraphQL for JavaScript
insomnia - The open-source, cross-platform API client for GraphQL, REST, WebSockets, SSE and gRPC. With Cloud, Local and Git storage.