Project Roadmap

[theguild-bot]

Hive roadmap

💡 This page's content and the list of tasks is synced automatically from The Guild's Notion. We are open sourcing our roadmap and tasks because we wish to build tools in the public, and allow developers to take part in the process of shaping the future of this library.
🚀 Feel free to share your thoughts, feedback and ideas with us.
👍 If you wish to show interest and help us prioritize tasks, use the 👍 on the issue.

Future

• Improve Native Federation Compatibility #3815
• more granular insight interval filtering #3836
• Schema Check UI: Show affected GraphQL Operation Documents #2442 👍 3
• Support @contracts or other form of filtering for federation projects #2662 👍 2
• Feature Request: Add filter by fieldname to schema explorer #2785 👍 1 👀 1
• Detailed Subscription/@live and Defer/Stream usage data #3290
• Remember breaking change approvals in the context of a pull request #2698
• Filter for @deprecated directive on Schema Explorer #1580 👍 2 👀 2
• Admin API for CRUD operations #2994 👀 1 ❤️ 1 🎉 1 🚀 1
• Restrict access control for users on project and target level #2073 👍 1
• document collection access control #2741
• Restrict access control for users on project and target level #2073 👍 1
• Default permissions for newly added users #2718 👍 3
• Evaluate vite/vite-plugin-ssr as a Next.js replacement #430
• hive as a persisted operations/documents store #659 👀 1
• Separate tokens permissions and allow to create operations reporting token only #124 👍 1
• Data Forwarding #718 👍 1
• Publish Apollo Router plugin crate #291
• Self-hosting versioning #2995 ❤️ 2
• personal document collections #2740
• Laboratory should have state saved in browser #2737
• Feature: Schema Ownership #2818 👍 3
• Add documentation on hive.json options.  #2037
• schema:check CLI: deduplicate output information #3179 👍 2
• don't refresh the whole page when clicking on a schema check #3180 👍 1
• stop proxy GraphQL requests from the app frontend through the Next.js route handler #2749
• refresh button on certain views #3178 👍 2
• print docker image version on startup #2393 👍 2
• Allow to re-run a check from Github UI #2658
• Conditional Breaking Changes date range should be limited based on the org's retention  #574
• Notify orgs on Slack about rate-limit events #180
• Support OIDC Connect Discovery document #716
• accept both /supergraph and / CDN url for apollo-router #3309
• Feature Request: Provide custom headers per-target to the external schema composer #2730
• local composition with CLI #2750 👍 1
• Static total request for Conditional Breaking Change setting #3018
• Feature Request: subgraph metadata (team, contact etc) #2747
• figure out apollo router hive versioning #3314
• Router plugin should retry fetch of schema #2739 👍 2
• Feature Request: Search operations and link types/fields to operations #2704
• optional configurable retention period for schema checks #3264
• GraphQL Hive CLI does not support linux / aarch64 at this time. #2683
• Schema push onboarding instructions #183
• Light mode #289
• Support for the Global Object Identification Specification (Node interface) #2444 👍 1
• Document Webhook format #128 👍 1 👀 1
• Error codes + dedicated pages #207
• https://github.com/the-guild-org/graphql-hive-deployment/issues/1160
• Audit log #1071
• Group of access scopes #1157
• show oidc endpoint errors to organization admins #1232
• Personal access tokens #1272
• Support Discord as a first-class notification/alert target #130 👀 1
• More alerts and notifications #253 👍 2
• Custom actions when publishing/checking the schema #254 👍 1
• Allow to download schema via CLI #678 👍 1 👀 2
• Break client package into library-specific packages #4571
• Persist errors and changes #1536 👍 2
• persist insights operation/client filter in url #4368
• Support MS Teams as a first-class notification/alert target  #4538 👍 2 ❤️ 1
• allow service url changes for schema check #3979
• permissions: prevent viewer role from creating new projects and targets #3978
• find oauth integration via organization name #4367 ❤️ 2
• Show reporting usage from previous months  #3929
• insights view for multiple targets data #4369
• Stitching composition result is not predictable #3897
• hive cli command for listing services (subgraphs) #3855
• support sorting insights on both request count and failure rate #3854 👍 1
• Rethink usage tracking of enum members for Hive App UI  #3818
• app schema explorer: use latest composable/valid schema version instead of latest schema version #3892
• support schema contracts for single schema projects #3856 👍 1
• Rethink usage tracking of union members for Hive App UI #3817
• Explorer: GraphQL Fields/Types (schema coordinate) detail view #2443 👍 1
• Allow to skip invalid GraphQL operations from being collected #2089
• Preflight script in Laboratory when querying API #3612 👍 2 👀 1
• External composition for other types of projects #3593 👍 2
• Bring back the sorting feature from the operations list #1597
• GraphQL Operations Detail Page #1579
• GraphQL Operations: filter by client name and client version #2441
• Timout errors should be visible by the user #1652
• Apollo Federation v2 schema composition #712
• Go lang client #474 👍 1
• Feature Request: Deep link to query in Laboratory #767 👍 1 ❤️ 1
• Persist schema checks  #333 👀 2
• Handle long list of github repositories in project settings #1440 👍 2
• Python client #508 👍 3
• Add 'presets' in tokens #959
• Possible improvement of ClickHouse Cloud performance #1129
• Laboratory: Query actual graph endpoints #788 👀 1
• Consider to drop the default personal organization  #98
• https://github.com/the-guild-org/graphql-hive-deployment/issues/1158

useHive

• useHive client plugin skip reporting for operation/request based on context value #3810 👍 2

[yanns]

What about #2449
Is it similar to #254 ?

[capaj]

is the order just random for the issues?

It would be nice to compile a list of like 10 or 20 most important issues to resolve sorted by importance. Currently I would like to pick something to work on while I wait for feedback, but I am not able to judge which issues are important.

[kamilkisiela]

I don't think we will ever have tasks sorted by importance in the roadmap here and if you need to pick up a next task, you can always talk to me and @n1ru4l :)

[capaj]

I don't think we will ever have tasks sorted by importance in the roadmap here

why not? Can you elaborate?

[kamilkisiela]

because priority is always changing and even if you have a task that is the most important to do, it could be a week long task or a tiny one, and not all of them can be done by anyone.