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

Documents in child folders not mapped to clients #572

Open
mhusseini opened this issue Dec 7, 2024 · 0 comments
Open

Documents in child folders not mapped to clients #572

mhusseini opened this issue Dec 7, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@mhusseini
Copy link
Contributor

Environment

  • Operating System: Darwin
  • Node Version: v20.4.0
  • Nuxt Version: 3.14.159
  • CLI Version: 3.15.0
  • Nitro Version: 2.10.4
  • Package Manager: [email protected]
  • Builder: -
  • User Config: -
  • Runtime Modules: -
  • Build Modules: -

Describe the bug

I have the following folder structure:

queries

  • clientA
    • generated
  • clientB
    • generated

All folders (clientA, client B and generated) contain .graphql files.

This is my configuration from nuxt.config.ts:

"graphql-client": {
        clients: {
            clientA: {
                host: "https://hosta.com/graphql",
            },
            clientB: {
                host: "https://hostb.com/graphql",
            },
        }

When I try to execute the queries inside those folders using useAsyncGql(), only the queries directly under the "clientA" und "clientB" folders are executed. When I inspect the generated code under .nuxt/gql/index.d.ts, I see that only the query files directly under the "clientA" and "clientB" folders where mapped to the respective clients (const GqClientOps = {"clientA":[...). The files under the "generated" folders are completely ignored.

Expected behaviour

I have expected the queries under the "generated" folders to be mapped to the respective clients so that I can execute the queries with useAsyncGql().

Reproduction

No response

Additional context

No response

Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant