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

[Feature] GraphQL API Support #1207

Open
vica-admin opened this issue Dec 31, 2024 · 0 comments
Open

[Feature] GraphQL API Support #1207

vica-admin opened this issue Dec 31, 2024 · 0 comments
Labels

Comments

@vica-admin
Copy link

Is your feature request related to a problem? Please describe.
REST APIs are useful, but GraphQL provides a more flexible and efficient way to query and manipulate data. Many modern tools and applications integrate seamlessly with GraphQL, and lacking this feature makes it harder to use Teable in a contemporary tech stack.

Describe the solution you'd like
I’d like Teable to offer a fully-featured GraphQL API, similar to what Directus or Hasura provides. This would enable users to define queries that fetch only the data they need, reduce over-fetching and under-fetching issues, and make the API more developer-friendly.

Describe alternatives you've considered

  • Using REST API workarounds, such as making multiple requests and filtering the data client-side, but this introduces inefficiencies and increases development time.
  • Building a custom GraphQL wrapper around the existing REST API, but this adds complexity and maintenance overhead.

Additional context
Adding GraphQL API support could help Teable attract a broader audience, including developers and teams already leveraging GraphQL in their projects. Below are examples of other platforms that effectively utilize GraphQL:

  • Directus: Offers a GraphQL API out of the box for easy querying and data management.
  • Hasura: Provides real-time GraphQL APIs for databases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants