You are here

Home » API reference » Deploy - Content Staging 7.2

TODO.txt in Deploy - Content Staging 7.2

Same filename and directory in other branches
  1. 5 TODO.txt
  2. 7.3 TODO.txt
GENERAL TODO'S
--------------

 * Conditionally integrate with Encrypt (http://drupal.org/project/encrypt) to
   store all config data for all authenticators.

 * Cosider making aggregators return full entities instead of keys. Views
   supports this with its function called something like
   $views->query->get_result_entities(). This could potentially save some code.

 * Better test coverage
     - Test the fetch-only functionality
     - Test the dashboard and other cruical UI elements like the "Deploy" button

 * Implement hook_help() where needed.

 * Implement granular permissions, including:
     - administer deployment plans
     - administer deployment endpoints
     - access deployment overview
     - make deployments

 * Make all plugins more private and isolate necessary methods and parameters
     - Oversee how plugins are sharing/add config between each other.
     - Oversee how default config keys should be set in plugin objects.

 * See if we can integrate with Entity API and hook_entity_property_info() in a
   way. Would be nice if we just could mark properties and fields as holding
   a dependency, eventually with a 'dependency callback' similar to the
   'getter callback'. This would save a lot of dependency code and make
   'hook_deploy_entity_dependency' redundant.

 * See if we really need to define plugins through hooks. Is $plugin enough
   maybe, like 'content_types' etc. are defined. Performance implications?

File

TODO.txt
View source 
  1. 

  2. GENERAL TODO'S

  3. --------------

  4. 

  5.  * Conditionally integrate with Encrypt (http://drupal.org/project/encrypt) to

  6.    store all config data for all authenticators.

  7. 

  8.  * Cosider making aggregators return full entities instead of keys. Views

  9.    supports this with its function called something like

  10.    $views->query->get_result_entities(). This could potentially save some code.

  11. 

  12.  * Better test coverage

  13.      - Test the fetch-only functionality

  14.      - Test the dashboard and other cruical UI elements like the "Deploy" button

  15. 

  16.  * Implement hook_help() where needed.

  17. 

  18.  * Implement granular permissions, including:

  19.      - administer deployment plans

  20.      - administer deployment endpoints

  21.      - access deployment overview

  22.      - make deployments

  23. 

  24.  * Make all plugins more private and isolate necessary methods and parameters

  25.      - Oversee how plugins are sharing/add config between each other.

  26.      - Oversee how default config keys should be set in plugin objects.

  27. 

  28.  * See if we can integrate with Entity API and hook_entity_property_info() in a

  29.    way. Would be nice if we just could mark properties and fields as holding

  30.    a dependency, eventually with a 'dependency callback' similar to the

  31.    'getter callback'. This would save a lot of dependency code and make

  32.    'hook_deploy_entity_dependency' redundant.

  33. 

  34.  * See if we really need to define plugins through hooks. Is $plugin enough

  35.    maybe, like 'content_types' etc. are defined. Performance implications?