Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to manage graphql settings #1420

Open
odiinnn opened this issue Jan 8, 2025 · 2 comments
Open

Add ability to manage graphql settings #1420

odiinnn opened this issue Jan 8, 2025 · 2 comments

Comments

@odiinnn
Copy link

odiinnn commented Jan 8, 2025

Problem / use case

Now we have small amount of graphql settings. Want to have access to full graphql settings. Currently we have to patch @ponder/core package to apply this settings.

Proposed solution

Adjust import { graphql } from "@ponder/core"; function to make access to all graphql settings. Want to add some more plugins, errors masking.

const defaultGraphqlOptions = { curent_options }

export const graphql = (options: YogaServerOptions = defaultGraphqlOptions) => {...}
@typedarray
Copy link
Collaborator

Thanks for opening. Likely open to adding this, but could you be more specific about which settings & plugins you'd like to use, and why? Will help us justify the expansion of our public API.

@odiinnn
Copy link
Author

odiinnn commented Jan 9, 2025

We have some features that we want implement on graphql side -

  1. Plugins. We have several custom plugins, also need to add request limiter, Prometheus and session plugins.
  2. Have ability to disable playground, for ex - in production mode
  3. Cors settings
  4. Adjust error handlings with maskedErrors handlers.
  5. It would be nice to add some sort of persisted queries
  6. Landing page settings

I understand that part of this feature requests can be done on server settings side, but graphql-yoga allow this without it, so it would be nice to have access to such settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants