Menus

Another common use case you will often need is to query a menu. This is particularly useful for use cases where you will want to control or add items via the backend in the Drupal administration interface.
Add the schema declaration
The first step, as seen in the introduction, is to add the types and fields in the schema. We can do this directly in the schema string in your own schema implementation (src/Plugin/GraphQL/Schema/SdlSchemaMyDrupalGql.php).
1
...
2
type Query {
3
    ...
4
    menu(name: String!): Menu
5
    ...
6
}
7
​
8
type Menu {
9
  name: String!
10
  items: [MenuItem]
11
}
12
​
13
type MenuItem {
14
  title: String!
15
  url: Url!
16
  children: [MenuItem]
17
}
18
​
19
type Url {
20
  path: String
21
}
22
​
23
...
Copied!
In this schema we can see that we can query a menu by its name. This will return a "Menu" type which includes a name field as well as a list of "MenuItem".
Adding resolvers
To add the resolvers we go to our schema implementation and call the appropriate data producers inside the getResolverRegistry method.
1
/**
2
 * {@inheritdoc}
3
 */
4
protected function getResolverRegistry() {
5
  ...
6
​
7
   // Menu query.
8
  $registry->addFieldResolver('Query', 'menu',
9
    $builder->produce('entity_load')
10
      ->map('type', $builder->fromValue('menu'))
11
      ->map('id', $builder->fromArgument('name'))
12
  );
13
​
14
  // Menu name.
15
  $registry->addFieldResolver('Menu', 'name',
16
    $builder->produce('property_path')
17
      ->map('type', $builder->fromValue('entity:menu'))
18
      ->map('value', $builder->fromParent())
19
      ->map('path', $builder->fromValue('label'))
20
  );
21
​
22
  // Menu items.
23
  $registry->addFieldResolver('Menu', 'items',
24
    $builder->produce('menu_links')
25
      ->map('menu', $builder->fromParent())
26
  );
27
​
28
  // Menu title.
29
  $registry->addFieldResolver('MenuItem', 'title',
30
    $builder->produce('menu_link_label')
31
      ->map('link', $builder->produce('menu_tree_link')
32
        ->map('element', $builder->fromParent()))
33
  );
34
​
35
  // Menu children.
36
  $registry->addFieldResolver('MenuItem', 'children',
37
    $builder->produce('menu_tree_subtree')
38
      ->map('element', $builder->fromParent())
39
  );
40
​
41
  // Menu url.
42
  $registry->addFieldResolver('MenuItem', 'url',
43
    $builder->produce('menu_link_url')
44
      ->map('link', $builder->produce('menu_tree_link')
45
        ->map('element', $builder->fromParent()))
46
  );
47
​
48
  $registry->addFieldResolver('Url', 'path',
49
    $builder->produce('url_path')
50
      ->map('url', $builder->fromParent())
51
  );
52
​
53
  ...
54
​
55
  return $registry;
56
}
Copied!
As we can see here we need to really provide all the fields with a resolver in order to have the data available, this can seem a bit unnecessary at first but it's a crucial step towards a cleaner API. In this case, we resolve the menu inside the Query type and from there we can start resolving each field from Menu and also MenuItem.

Queries - Previous

Entity references

Next - Queries

Routes

Last modified 1yr ago

Copy link

Contents

Add the schema declaration

Adding resolvers