hasura-cms
gqless
| hasura-cms | gqless | |
|---|---|---|
| 1 | 10 | |
| 4 | 3,672 | |
| - | 0.0% | |
| 3.6 | 0.0 | |
| about 3 years ago | about 2 years ago | |
| TypeScript | TypeScript | |
| - | GNU General Public License v3.0 only |
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.
hasura-cms
-
REST vs. gRPC vs. GraphQL
Hasura makes that pretty easy as can be seen here: https://github.com/firatoezcan/hasura-cms
This is also easy to do with self-written servers, maybe take a look at the metadata folder to get a gist of what Hasura would be doing behind the scenes (running a query and then checking the claim for the condition for the given field that permission wants to be requested for)
(Just a repo I started one evening, it doesn't do much but the concept of projects with owners and collaborators should work)
gqless
-
graphql-code-generator VS gqless - a user suggested alternative
2 projects | 2 Jun 2023
-
GraphQL code generator, how to make query without existing document?
Maybe GQLess is for you? It's a client that magically creates a query from they way you use objects in your react components.
-
Instant realtime GraphQL with built-in authorization for SQL Server
Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too.
https://github.com/hasura/graphql-engine/issues/6991
General support for inherited roles is one of the things I'm most excited about because it makes a bunch of hard things around reusing and composition so easy.
This improvement plays really well along with things like "role-based schemas" so that GraphQL clients have access to just the exact GraphQL schema they should be able to access - which is in turn composed by putting multiple scopes together into one role.
Also interesting is how well this could play with other innovations on the GraphQL client ecosystem like gqless[1] and graphql-zeus[2] because now there's a typesafe and secure SDK for really smooth developer experience on the client side.
[1]: https://github.com/gqless/gqless
- GQless: A GraphQL client built for rapid iteration
-
Hacker News top posts: Jun 2, 2021
GQless: A GraphQL client built for rapid iteration\ (6 comments)
- GQless – a GraphQL client built for rapid iteration
-
Ask HN: What novel tools are you using to write web sites/apps?
Cannot recommend gqless highly enough for making graphql actually fun to use and closer to something like meteor/firebase syntax[0].
And I’ll self-promote, but I’ve been working on what I consider to be a “next generation” style system for React that solves my biggest issue with it currently: being able to performantly write styles in a nice syntax that optimize for both web and native. Called SnackUI, though it’s still in beta[1].
[0] https://gqless.com
[1] https://github.com/snackui/snackui
-
REST vs. gRPC vs. GraphQL
On the GraphQL side you can use gqless[0] (or the improved fork I helped sponsor, here[1]). It's by far the best DX I've had for any data fetching library: fully typed calls, no strings at all, no duplication of code or weird importing, no compiler, and it resolves the entire tree and creates a single fetch call.
[0] https://github.com/gqless/gqless
[1] https://github.com/PabloSzx/new_gqless