spring-projects / spring-projects/spring-graphql

Schema inspection support for QueryDsl and QueryByExample auto registrations

Open
#970 1 comment 0 reactions 1 assignee View on GitHub

@rstoyanchev is already working on this.

Since May 21, 2024.

type: enhancement
Dominant language
Java
Stars
1.6k
Forks
336
PR merge metrics
No merged PRs in 30d

Description

I am using Spring Boot Parent 3.2.5 and a repository defined like the following:

@GraphQlRepository
public interface AssetRepository extends CrudRepository<Asset, Long>, QueryByExampleExecutor<Asset> {
}

I also have a graphqls schema that looks like the following:

type Query {
	assets(asset: AssetInput!): [Asset]
}

input AssetInput {
	assetuid: ID
	assetnum: String
}

type Asset {
	assetuid: ID
	assetnum: String
}

When I run the code, it works fine and returns results as expected. However the GraphQL schema inspection shows a log that shows this:

GraphQL schema inspection:
	Unmapped fields: {Query=[assets]}
	Unmapped registrations: {}
	Skipped types: []

If I register the data fetcher directly, the inspection does not show the error but from reading the docs and from monitoring the behavior, I would believe that it is configured appropriately and everything should be configured correctly. I'm not sure if this is a bug or an error on my part but wanted to create an issue here as I could not find similar issues.

Also the documentation doesn't have a really clear example of getting QBE working but with trial and error I came to this implementation so if my knowledge is incorrect please correct me.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.