Created
November 28, 2019 14:08
-
-
Save AugustoPedraza/3f6f7e6d9549c658194238d7109ad5f3 to your computer and use it in GitHub Desktop.
Capture form GQL
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| query { | |
| captureForm(shortId: "an id") { | |
| account { | |
| avatarUrl | |
| isVerified | |
| } | |
| afterSubmission | |
| avatarMedia { | |
| extensionType | |
| sourceUuid | |
| uri | |
| } | |
| coverMedia { | |
| extensionType | |
| sourceUuid | |
| uri | |
| } | |
| instructionsText | |
| subtitle | |
| title | |
| questions(first:50) { | |
| edges { | |
| node { | |
| textContent | |
| } | |
| } | |
| } | |
| } | |
| } |
Not sure what you mean.
If you're talking about our future GQL schema. The answer is yes, we will have a bigger schema. But, for finish the associated dev task, this have all the required fields for that specific scope.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have more fields, don't we?