graphql / graphql/graphiql

[graphiql] Navigation to field defined in type extension is "disabled"

Open
#3,114 1 comment 0 reactions 0 assignees View on GitHub
bug graphql-language-service lsp-server
Dominant language
TypeScript
Stars
16.9k
Forks
1.9k
Avg merge
22h 45m
Merged PRs (30d)
70

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

Given the modular schema:
**users module**
`- modules/users/user.gql`
```gql
type User {
name: String
nicknames: [Nickname]
}
```
`- modules/users/nick-name.gql`
```gql
type Nickname {
name: String!
source: User!
}
```
`- modules/users/query.gql`
```gql
extend type Query {
me: User!
}
```
**authorization module**
`- modules/authorization/user.gql`
```gql
extend type User {
roles: [Role]
}
```
`-module/authorization/role.gql`
```gql
type Role {
id : ID!
name: String
}
```
Given the query document
`- queries/me.gql`
```gql
query {
me {
name
nicknames {
name
}
roles {
name
}
}
}
```
✔️ When I `ctrl+click` `query.me` `modules/users/query.gql` is opened in the editor.
✔️ When I `ctrl+click` `query.me.name` `modules/users/user.gql` is opened in the editor.
✔️ When I `ctrl+click` `query.me.nicknames` `modules/users/user.gql` is opened in the editor.
❌ When I `ctrl+click` `query.me.roles` nothing happens (however, there is basic intellisense). Expect `modules/authorization/user.gql` to be opened in the editor.
✔️ When I `ctrl+click` `query.me.role.name` `modules/authorization/role.gql` is opened in the editor.

### Expected Behavior

I should be able to `ctrl+click` (Navigate) to a field defined in and extended type.

### Steps To Reproduce

```Markdown
module.exports = {
schema: "./modules/**/*.gql",
documents: [
"./queries/**/*.gql",
]
};
```

### Module pattern

- [ ] graphiql-umd
- [ ] graphiql-esm
- [ ] graphiql-commonjs

### Environment

```Markdown
- GraphiQL Version: latest
- OS: Windows 10
- Browser: Edge
- Bundler: Webpack
- `react` Version: ^18.2.0
- `graphql` Version: ^16.6.0
```

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.