---
# This file defines the capabilities exposed by the plugin. This file is mandatory
# for a plugin to be considered as valid.

# Define the main module of the plugin. In this module you can define the build method
# if the plugin exposes a build (actually a post build hook occurring after the files
# are "detemplatized")
:plugin_module: <%= plugin_module_name %>

# In the processors defined in the hereunder hash you map a subcommand with the processor 
# that will handle it. A plugin can define as many subcommands as needed, or none...
# Hash keys should match sub-commands declared in the `command_line.yaml` file and processor 
# classes should expose an `execute` method.
:processors:
  <%= plugin_name %>: <%= plugin_module_name %>::Processor

# This is the name of the method called after the files are detemplatized. This method has
# to be a module method in the `plugin_module` module.
:build: post_build_hook

# If a dsl module is declared it will be injected in the DSL available in the shell or templates
:dsl:
  - <%= plugin_module_name %>::Dsl::<%= plugin_module_name %>Dsl

# These are the files (array) defining entity types. These files should not be already 
# required by the plugin as they will be required by the framework when needed.
:entity_definitions:
  - <%= plugin_name %>/entity_definitions/<%= plugin_name %>_entity

# A list of root directories where you can find templates in directories named from the
# entity types they are attached to. 
:templates:
  - etc/templates

# Plugin dependencies to other plugins. Use the plugin name and NOT the plugin
# gem name (in the case of a gem plugin). Declare as well dependencies to local plugins.
:dependencies: []