graphweaver

5 ms·

1.
Show HN: Graphweaver v1: Instant GraphQL with Auth, Admin UI and Federation(github.com)
1 points by graphweaver 2y ago|0 comments
2.
by graphweaver 3y ago
Thanks this is what we have on filters so far: https://graphweaver.com/docs/filters-and-operators The aggregates package looks very interesting, we would love to see something similar for Graphweaver.
3.
by graphweaver 3y ago
We appreciate all the hard work that Hasura has done to make GraphQL a main stream technology.
4.
by graphweaver 3y ago
Here are some links around security: https://graphweaver.com/docs/adding-local-authentication https://graphweaver.com/docs/implementing-authorization https://graphweaver.com/docs&#
5.
by graphweaver 3y ago
We have done performance testing when releasing client projects but nothing that directly compares Graphweaver to competitors. I will add this to the list for us to do.
6.
by graphweaver 3y ago
Great can you point me to the filtering/grouping capabilities? I will take a look.
7.
by graphweaver 3y ago
We actually do that with the Contentful integration we’ve built. It dynamically reads the schema then creates the API.
8.
by graphweaver 3y ago
Not everyone will see TS as an advantage but there are many who will.
9.
by graphweaver 3y ago
Yeah sorry will address it directly. Graphweaver is different in a number of ways: - Graphweaver is not just Postgres, you can run it connected to only MySQL - Graphweaver can connect to one or more datasources. You can even connect both My
10.
by graphweaver 3y ago
We add validation using https://github.com/typestack/class-validator . I will make sure we get this documented.
11.
by graphweaver 3y ago
We have used postgres with every client deployment so far, it's our go to relational db. We have also needed to connect to a 2nd or 3rd data source on every project. So the power is when you combine these data sources.
12.
by graphweaver 3y ago
With Wundergraph, you define schema first. This generates types and hooks that you can then use on the front end. The production API is not a GraphQL API its Rest I believe. Graphweaver also generate types and react hooks for the front end,
13.
by graphweaver 3y ago
The main difference is Graphweaver is code-only approach with Typescript. GraphQL Mesh is a schema-first approach. Both great projects, different philosophies.
14.
by graphweaver 3y ago
Yeah it is comparable: - We are 100% open source. - Written in Typescript. - We support any data source directly in the server process, either with pre-built data providers or build your own. - We support cross data source filtering (get or
15.
by graphweaver 3y ago
You're right we need to improve the documentation on this. We do have an example though: https://github.com/exogee-technology/graphweaver/tree/main/s... We have also added the OpenAPI spec on the ro
16.
by graphweaver 3y ago
Nothing out-of-the-box for this yet. We have actually done this for our clients, but it has been a custom field resolver: https://graphweaver.com/docs/graphql-entities-and-resolvers#...
17.
by graphweaver 3y ago
Thanks for all your hard work skeep!
18.
by graphweaver 3y ago
We agree, with any GraphQL API you need to make sure it is hardened for production. We are looking to add more on documentation on this soon and maybe a tutorial series on exactly this.
19.
by graphweaver 3y ago
We have some docs on that here: https://graphweaver.com/docs/implementing-authorization The auth is at the access control is at the API layer.
20.
by graphweaver 3y ago
This is true but like with any build there are many decisions to make. We have settled on this stack for our API's and we think others will find it useful.
21.
Show HN: Graphweaver – Instant GraphQL API on Postgres, MySQL, SQLite and More(github.com)
74 points by graphweaver 3y ago|48 comments