{% import '@lib/di.twig' as di %}
<?php

declare(strict_types=1);

namespace Drupal\{{ machine_name }}\Plugin\Menu;

{% apply sort_namespaces %}
use Drupal\Core\Menu\MenuLinkDefault;
  {% if services %}
{{ di.use(services) }}
use Drupal\Core\Plugin\ContainerFactoryPluginInterface;
use Symfony\Component\DependencyInjection\ContainerInterface;
  {% endif %}
{% endapply %}

/**
 * @todo Provide description for this class.
 *
 * @DCG
 * Typically a module-defined menu link relies on
 * \Drupal\Core\Menu\MenuLinkDefault class that builds the link using plugin
 * definitions located in YAML files (MODULE_NAME.links.menu.yml). The purpose
 * of having custom menu link class is to make the link dynamic. Sometimes, the
 * title and the URL of a link should vary based on some context, i.e. user
 * being logged, current page URL, etc. Check out the parent classes for the
 * methods you can override to make the link dynamic.
 *
 * @DCG It is important to supply the link with correct cache metadata.
 * @see self::getCacheContexts()
 * @see self::getCacheTags()
 *
 * @DCG
 * You can apply the class to a link as follows.
 * @code
 * foo.example:
 *   title: Example
 *   route_name: foo.example
 *   menu_name: main
 *   class: \Drupal\foo\Plugin\Menu\FooMenuLink
 * @endcode
 */
final class {{ class }} extends MenuLinkDefault {% if services %}implements ContainerFactoryPluginInterface {% endif %}{

{% if services %}
  /**
   * Constructs a new {{ class }} instance.
   */
  public function __construct(
    array $configuration,
    $plugin_id,
    $plugin_definition,
{{ di.signature(services) }}
  ) {
    parent::__construct($configuration, $plugin_id, $plugin_definition);
  }

  /**
   * {@inheritdoc}
   */
  public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition): self {
    return new self(
      $configuration,
      $plugin_id,
      $plugin_definition,
{{ di.container(services) }}
    );
  }

{% endif %}
}