Graphql-public-schema-filter Alternatives

graphql-public-schema-filter reviews and mentions

• Public and Private GQL APIs pointing to same Unified graph?
  1 project | /r/graphql | 18 Apr 2023
• Keeping parts of your GraphQL schema hidden from Introspection
  1 project | /r/graphql | 15 Jun 2022

  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
  2 projects | /r/graphql | 31 Jan 2022

  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?
  1 project | /r/graphql | 28 Dec 2021

  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
  1 project | /r/graphql | 4 Dec 2021

  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?
  2 projects | /r/graphql | 18 Nov 2021

  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
  12 projects | dev.to | 29 Jul 2021

  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
  1 project | /r/graphql | 28 Jul 2021
• A note from our sponsor - InfluxDB
  www.influxdata.com | 26 Apr 2024

  Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →