-
Notifications
You must be signed in to change notification settings - Fork 233
fix: fix selecting parent of unique nodes #2592
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
Closed
devsergiy
wants to merge
2
commits into
main
from
sergiy/eng-9097-fix-wrong-external-parent-selection-when-use-interfaces
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
github.com/wundergraph/graphql-go-tools v2.0.0-rc.259 commit 726700149835 changelog💡 Result:
726700149835(subject): “fix selecting parent of unique nodes” — changesv2/pkg/engine/plan/datasource_filter_visitor.goto stop walking up the parent chain when the parent is fully external (it now breaks instead of continuing). [3]Sources: [1] Tags page (rc.259 notes), [2] Release page v2.0.0-rc.259, [3] Commit 726700149835.
🌐 Web query:
wundergraph graphql-go-tools v2 "parent of unique nodes" fix rc.259💡 Result:
In
wundergraph/graphql-go-toolsv2, the GitHub tag/releasev2.0.0-rc.259(dated 2026-03-05) contains a single listed bug fix:nullinstead of making unnecessary calls. [1], [2]I couldn’t find any release note, PR title, or commit message in
rc.259that matches the exact phrase “parent of unique nodes”. If you can paste the exact error/log line (or link the issue/PR), I can track the specific fix to the right tag/commit.Sources: [1], [2]
🌐 Web query:
site:github.com wundergraph graphql-go-tools/v2 rc.259 rc.257 commits💡 Result:
Commits included in wundergraph/graphql-go-tools between v2.0.0-rc.257 and v2.0.0-rc.259 (i.e.,
v2.0.0-rc.257...v2.0.0-rc.259) are these 5 commits: [1]6fa1cdb— chore: move cost tests into separate file (PR#1418) [1]3b4dbcb— fix: handle complex types inside inline fragments in gRPC execution plan (PR#1411) [1]0bc474f— chore(master): release 2.0.0-rc.258 (PR#1425) [1]5885c48— fix: skip invocation for empty context in field resolvers (PR#1413) [1]5940d31— chore(master): release 2.0.0-rc.259 (PR#1427) [1]The tags page also shows v2.0.0-rc.258 and v2.0.0-rc.259 were both created on Mar 5, 2026, with their release PRs (
#1425,#1427) matching the commits above. [2]Sources: [1] [2]
Clarify that the pinned commit contains the intended fix but is not in the rc.259 release notes.
The pseudo-version pins to commit
726700149835which contains "fix selecting parent of unique nodes", but this fix is not listed in the v2.0.0-rc.259 (2026-03-05) changelog. The official rc.259 release documents only "skip invocation for empty context in field resolvers" (commit 5885c48). Confirm that commit726700149835is the correct intended fix before merge and verify it does not introduce regressions to the field resolver logic changes.🤖 Prompt for AI Agents