Skip to content

feat: use hive lab instead of graphiql#2006

Draft
mskorokhodov wants to merge 2 commits intomainfrom
enhancement/hive-lab-lib
Draft

feat: use hive lab instead of graphiql#2006
mskorokhodov wants to merge 2 commits intomainfrom
enhancement/hive-lab-lib

Conversation

@mskorokhodov
Copy link
Collaborator

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @mskorokhodov, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request transitions the GraphQL gateway's interactive development environment from GraphiQL to Hive Lab. This enhancement provides users with an updated and potentially more feature-rich interface for interacting with the GraphQL API, improving the developer experience by leveraging the new rendering capabilities.

Highlights

  • GraphQL IDE Switch: The interactive GraphQL interface has been switched from GraphiQL to Hive Lab. This involves updating the relevant rendering library in the gateway package.
  • Dependency Management: A new dependency, @graphql-yoga/render-laboratory, has been added to the gateway's package.json, and the yarn.lock file has been updated to reflect this change and other related dependency resolutions.
Changelog
  • packages/gateway/package.json
    • Added @graphql-yoga/render-laboratory as a development dependency.
  • packages/gateway/src/cli.ts
    • Replaced the import of renderGraphiQL with renderLaboratory.
    • Updated the defaultOptions.renderGraphiQL to use renderLaboratory.
  • yarn.lock
    • Added a new entry for @graphql-yoga/render-laboratory with its resolution details.
    • Updated various workspace dependency resolutions, including @apollo/rover, @graphql-hive/gateway, @graphql-hive/logger, @graphql-mesh/hmac-upstream-signature, @graphql-mesh/plugin-jwt-auth, and @graphql-mesh/transport-ws.
Activity
  • No human activity (comments, reviews) has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request switches the default GraphQL IDE from GraphiQL to Hive Laboratory. The implementation in packages/gateway/src/cli.ts is well-done, preserving backward compatibility by reassigning the renderGraphiQL default option. However, the new dependency in packages/gateway/package.json uses a local file path, which will cause issues in CI/CD environments and for other developers. I've added a comment to address this.

"@graphql-tools/load": "^8.1.6",
"@graphql-tools/utils": "^11.0.0",
"@graphql-yoga/render-graphiql": "^5.16.2",
"@graphql-yoga/render-laboratory": "../../../graphql-yoga/packages/render-laboratory",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This dependency uses a local file path, which is not suitable for a package intended for publication. It will cause installation failures for anyone who doesn't have the graphql-yoga repository at the same relative path. Please replace this with a version from a package registry (like npm) or use a workspace reference (e.g., workspace:*) if this package is part of the same monorepo.

@enisdenjo enisdenjo marked this pull request as draft February 24, 2026 17:25
@mskorokhodov mskorokhodov force-pushed the enhancement/hive-lab-lib branch from d7ec4a8 to c6045c6 Compare February 24, 2026 20:22
@theguild-bot
Copy link
Collaborator

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@graphql-hive/gateway 2.4.3-alpha-b8d008330c45653cf6e40e27d1e7bda618532c1f npm ↗︎ unpkg ↗︎
@graphql-hive/nestjs 2.0.40-alpha-b8d008330c45653cf6e40e27d1e7bda618532c1f npm ↗︎ unpkg ↗︎

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

Successfully merging this pull request may close these issues.

2 participants