galactagraph-boilerplate
graphql-public-schema-filter
galactagraph-boilerplate | graphql-public-schema-filter | |
---|---|---|
4 | 8 | |
11 | 52 | |
- | - | |
0.0 | 4.2 | |
over 2 years ago | 3 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
galactagraph-boilerplate
- Any GraphQL issues the community would like to be solved?
- GalactaGraph - Apollo Federation GraphQL Boilerplate to help you set-up your federated API [Looking for Feedback/PRs Welcome!]
-
GalactaGraph - Apollo Federation GraphQL Boilerplate to help you set-up your federated API [Looking for Feedback!]
Recently I dived into the world of Apollo Federation, and after countless hours eating documentation and breaking docker instances, I came up with a handy boilerplate that tries to shave off some redundant code and add out-of-the-box features to an Apollo Federation powered GraphQL API: https://github.com/emanuele-moricci/galactagraph-boilerplate
graphql-public-schema-filter
- Public and Private GQL APIs pointing to same Unified graph?
-
Keeping parts of your GraphQL schema hidden from Introspection
We actually built the following package, @n1ru4l/graphql-public-schema-filter which solves the problem stated within the blog post in a similar way (by filtering an existing schema into a subset of the original schema).
-
Authorization by entities
I am using this technique in one of my projects where we have a public API that is a subset of the internal API. I open sourced the library for doing that: https://github.com/n1ru4l/graphql-public-schema-filter
-
Ideas for implementing admin authentication for only a few mutations?
I built something similar that is "metaframework"-agnostic https://github.com/n1ru4l/graphql-public-schema-filter. Using this method has its benefits and drawbacks. If you simply public and internal part of the schema it can work pretty well. We use it for hiding the internal API from the public customer facing integration API. It is definetly easier than makntaining two seperate GraphQL schemas. However, if you want full inteospection capabilities doing this can be confusing as the introspection query operation result is different based on the authorization header which moght be weird if you are using tools such as code generators, as you now have to do it for two different schemas.
-
When to use multiple endpoints in GraphQL
While building an GraphQL API that powers web applications we introduced a public customer-facing API. Instead of building two separate endpoints we chose to serve a different schema based on the authorization header. Furthermore, requests that do not provide an customer kntegration authorization header are only allowed to execute persisted operations. That way we somehow avoided having multiple HTTP routr endpoints. Instead of building two schemas from scratch and because the public schema is basically a filtered down version of the full graph we decided to filter down the graph using directive annotations on the schema SDL. I open sourced rhe JavaScript library for doing that (which is based upon graphql-tools). The dynamic schema selection based on the authorization header is done with Envelop
-
Any GraphQL issues the community would like to be solved?
graphql-public-schema-filter: This library allows you to filter down you big graphql schema into a smaller subgraph. I have been using this for filtering our big production schema down into a public api schema that our customers use. So they don't have access to all the internal types, that are only for our internal web applications. The great thing about this is that we can just serve the correct schema based on the authorization headers as API users and Web Application tokens differ. If you have one big monolithic GraphQL server this is a great way of doing this and we are quite happy with it.
-
Introducing Envelop - The GraphQL Plugin System
Public schema filter - for creating a simple GraphQL schema that can be used for public APIs based on existing GraphQL schema.
- I built a small library for filtering a GraphQL schema graph into a subgraph
What are some alternatives?
TNG - 📝 [Snippets] Typescript - Next.js/Nestjs - GraphQL
nestjs-graphql - GraphQL (TypeScript) module for Nest framework (node.js) 🍷
blog-graphql-nestjs-fileupload - example code on how to upload a file with multipart requests to GraphQL in nestjs
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.
paperhouses - Airbnb like web app built with React, TypeScript, GraphQl and Express.js
envelop - Envelop is a lightweight library allowing developers to easily develop, share, collaborate and extend their GraphQL execution layer. Envelop is the missing GraphQL plugin system.
graphql-node-typescript-prisma
graphql-jit - GraphQL execution using a JIT compiler
dockest - Docker + Jest integration testing for Node.js
graphql-helix - A highly evolved GraphQL HTTP Server 🧬
fpl-watch-server - The backend for FPL Watch. It uses GraphQL, Apollo, Postgres, TypeScript, Node, and MikroORM. 🥅
redwood - The App Framework for Startups