header.component.yml

Same filename in other branches
  1. 10 core/profiles/demo_umami/themes/umami/components/header/header.component.yml
core/profiles/demo_umami/themes/umami/components/header/header.component.yml

File

core/profiles/demo_umami/themes/umami/components/header/header.component.yml

View source
  1. # This is so your IDE knows about the syntax for fixes and autocomplete.
  2. $schema: https://git.drupalcode.org/project/drupal/-/raw/HEAD/core/assets/schemas/v1/metadata.schema.json
  3. # The human readable name.
  4. name: Umami header
  5. # Status can be: "experimental", "stable", "deprecated", "obsolete".
  6. status: experimental
  7. # Schema for the props. We support www.json-schema.org. Learn more about the
  8. # syntax there.
  9. props:
  10. # Props are always an object with keys. Each key is a variable in your
  11. # component template.
  12. type: object
  13. properties:
  14. attributes:
  15. type: Drupal\Core\Template\Attribute
  16. title: Attributes
  17. description: Wrapper attributes.
  18. label:
  19. type: string
  20. # Slots always hold arbitrary markup. We know that beforehand, so no need for
  21. # a schema for slots.
  22. slots:
  23. # The key is the name of the slot. In your template you will use
  24. # {% block content %}.
  25. logo:
  26. title: Logo
  27. dropdown:
  28. title: Dropdown
  29. # This is how you take control of the keys in your library
  30. # declaration. The overrides specified here will be merged (shallow merge) with
  31. # the auto-generated library. The result of the merge will become the library
  32. # for the component.
  33. libraryOverrides:
  34. # Once you add a key in the overrides, you take control of it. What you type
  35. # here is what will end up in the library component.
  36. dependencies:
  37. - core/drupal
  38. - core/once

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.