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

Router path planning fails if an alias with name id is used #1439

Open
alexus37 opened this issue Dec 12, 2024 · 2 comments
Open

Router path planning fails if an alias with name id is used #1439

alexus37 opened this issue Dec 12, 2024 · 2 comments
Assignees
Labels
bug Something isn't working internally-reviewed The issue has been reviewed internally.

Comments

@alexus37
Copy link

alexus37 commented Dec 12, 2024

Component(s)

router

Component version

v0.0.0-20240927172855-3e390cd5cf6c

router version

v0.0.0-20240927172855-3e390cd5cf6c

What happened?

Description

when I am using an alias with name id the path planner fails.

Steps to Reproduce

Create two subgraphs

  1. Which implements the repository entry point
  2. another on which supports the repository entity and the defaultBranchRef object

and run the following query

query {
  repository(owner: "<REDACTED>", name: "<REDACTED>") {
    defaultBranchRef {
      id
    }
    id: databaseId
  }
}

Expected Result

The correct query plan is returned.

Actual Result

The router errors

Log output

ERROR: 1 error occurred:\n\t* printOperation: validation failed: external: differing fields for objectName 'id' on (potentially) same type, locations: [], path: [query,repository]\n\n
@alexus37 alexus37 added the bug Something isn't working label Dec 12, 2024
Copy link

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

@YassineElbouchaibi
Copy link
Contributor

Sounds like it may originate from the same code change mentioned in #1440. If you can afford rolling back to router v0.107.3, it would probably solve your issue until a fix is made

@Noroth Noroth added the internally-reviewed The issue has been reviewed internally. label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internally-reviewed The issue has been reviewed internally.
Projects
None yet
Development

No branches or pull requests

4 participants