Conversation
Summary of ChangesHello @ardatan, 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 introduces an asynchronous execution mechanism for handling leftover fields within the Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request addresses a circular dependency issue by making a recursive call to handleLeftOver asynchronous using setImmediate. This is a good approach to prevent stack overflow errors. However, my review points out a potential portability issue with using setImmediate, as it is a Node.js-specific API, and suggests using setTimeout(..., 0) for better cross-environment compatibility.
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@graphql-tools/batch-delegate |
10.0.6-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/delegate |
12.0.0-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/federation |
4.2.4-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/fusion-runtime |
1.6.0-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/gateway |
2.1.20-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/nestjs |
2.0.25-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/plugin-aws-sigv4 |
2.0.18-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/plugin-opentelemetry |
1.2.2-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/plugin-prometheus |
2.1.6-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/router-runtime |
1.1.0-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/gateway-runtime |
2.3.6-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitch |
10.1.4-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitching-directives |
4.0.6-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/gateway-testing |
2.0.6-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/wrap |
11.1.0-alpha-9ffa8618e82774af879eab5dd71e0fd222e96cb7 |
npm ↗︎ unpkg ↗︎ |
🚀 Snapshot Release (Bun Docker Image)The latest changes of this PR are available as image on GitHub Container Registry (based on the declared |
🚀 Snapshot Release (Node Docker Image)The latest changes of this PR are available as image on GitHub Container Registry (based on the declared |
This fixes
requires-circularfailure on audit repositoryWeirdly this case was already passing here while failing in the upstream repo