📝 Edit page
            
    âž• Add page
            
    
         
    
    
    
    
        
            
 
        
    Basics
From Queries and Mutations section of the GraphQL learn docs.
Field
{
  hero {
    name
  }
}
{
  hero {
    name
    friends {
      name
    }
  }
}
Lists
Most of the time when you get a list, you’ll have to specify pagination boundaries, which are covered below. See more in Arguments and Paging.
Edges and nodes
{
	foo (first: 100) {
		edges {
			node {
				name
			}
    		}
	}
}
Nodes
{
	foo (first: 100) {
		nodes {
			name
    		}
	}
}
Arguments
No arguments - use default values, or get an error if it is required.
{
  human {
    name
    height
  }
}
{
  human(id: "1000") {
    name
    height
  }
}
Here we change from metres to feet.
{
  human(id: "1000") {
    name
    height(unit: FOOT)
  }
}
More complex params as a dictionary:
{
	viewer {
		repositories(
			first: 100,
			ownerAffiliations: OWNER,
			privacy: PUBLIC,
			orderBy: { field: UPDATED_AT, direction: DESC })
	}
}
Aliases
An alias is necessary to avoid an error on duplicate key. By default each one below would have the key "hero".
{
  empireHero: hero(episode: EMPIRE) {
    name
  }
  jediHero: hero(episode: JEDI) {
    name
  }
}
Operation names
- Basic
    - queryis implied and there is no query name.- { hero { name friends { name } } }
 
- Specific
    - This helps in production apps including when viewing a debug message.
        query HeroNameAndFriends { hero { name friends { name } } }
 
- This helps in production apps including when viewing a debug message.