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

feat: customize selection in call #1818

Closed
tusharmath opened this issue May 1, 2024 · 2 comments
Closed

feat: customize selection in call #1818

tusharmath opened this issue May 1, 2024 · 2 comments
Labels
state: inactive No current action needed/possible; issue fixed, out of scope, or superseded.

Comments

@tusharmath
Copy link
Contributor

Currently in call we can not specify what we need and how deeply nested query we need to issue.

For eg: If we wish to compose f and g using call this is how we set the steps:

type Query {
  f(a: Int, b: Int): F

  g(a: Int, b: Int): G

  fg: H @call(
      steps: [
        { query: "f", args: { a: 1, b: 2 }}
        { query: "g", args: { a: "{{value.fa}}", b: "{{value.fb}}" }}
      ]
    )
}

type F {
  fa: Int
  fb: String
  fc: Boolean
}

type G {
  ga: Int
  gb: String
  gc: Boolean
}

But while calling f or g we don't specify what fields need to be queried for. We wish to change that by providing a field called select.

type Query {
  f(a: Int, b: Int): F
  g(a: Int, b: Int): G
  fg: FG
    @call(
      steps: [
        { query: "f", args: { a: 1, b: 2 }, selection: "{fa fb}" }
        { query: "g", args: { a: 1, b: 2 }, selection: "{ga gb}" }
      ]
    )
}

type F {
  fa: Int
  fb: String
  fc: Boolean
}

type G {
  ga: Int
  gb: String
  gc: Boolean
}
Copy link

Action required: Issue inactive for 30 days.
Status update or closure in 7 days.

@github-actions github-actions bot added the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label May 31, 2024
Copy link

github-actions bot commented Jun 7, 2024

Issue closed after 7 days of inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: inactive No current action needed/possible; issue fixed, out of scope, or superseded.
Projects
None yet
Development

No branches or pull requests

1 participant