child properties WIP

tripal_chado/includes/TripalFields/local__child_properties/local__child_properties.inc

@@ -9,77 +9,19 @@
  */
 class local__child_properties extends ChadoField {
 
-  // --------------------------------------------------------------------------
-  //                     EDITABLE STATIC CONSTANTS
-  //
-  // The following constants SHOULD be set for each descendant class.  They are
-  // used by the static functions to provide information to Drupal about
-  // the field and it's default widget and formatter.
-  // --------------------------------------------------------------------------.
-  /**
-   * The default label for this field.
-   */
   public static $default_label = 'Child Properties';
-
-  /**
-   * The default description for this field.
-   */
   public static $default_description = 'All of the properties associated with child features.';
-
-  /**
-   * The default widget for this field.
-   */
   public static $default_widget = 'local__child_properties_widget';
-
-  /**
-   * The default formatter for this field.
-   */
   public static $default_formatter = 'local__child_properties_formatter';
-
-  // The module that manages this field.
-  // If no module manages the field (IE it's added via libraries)
-  /**
-   * Set this to 'tripal_chado'.
-   */
-  public static $module = 'tripal_manage_analyses';
-
-  // A list of global settings. These can be accessed within the
-  // globalSettingsForm.  When the globalSettingsForm is submitted then
-  // Drupal will automatically change these settings for all fields.
-  // Once instances exist for a field type then these settings cannot be.
-  /**
-   * Changed.
-   */
+  public static $module = 'tripal_chado';
   public static $default_settings = [
     'storage' => 'field_chado_storage',
-    // It is expected that all fields set a 'value' in the load() function.
-    // In many cases, the value may be an associative array of key/value pairs.
-    // In order for Tripal to provide context for all data, the keys should
-    // be a controlled vocabulary term (e.g. rdfs:type). Keys in the load()
-    // function that are supported by the query() function should be
-    // listed here.
     'searchable_keys' => [],
   ];
-
-  // Indicates the download formats for this field.  The list must be the.
-
-  /**
-   * Name of a child class of the TripalFieldDownloader.
-   */
   public static $download_formatters = [
     'TripalTabDownloader',
     'TripalCSVDownloader',
   ];
-
-  // Provide a list of instance specific settings. These can be access within
-  // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instance.
-  // It is recommended to put settings at the instance level whenever possible.
-  // If you override this variable in a child class be sure to replicate the
-  // term_name, term_vocab, term_accession and term_fixed keys as these are.
-  /**
-   * Required for all TripalFields.
-   */
   public static $default_instance_settings = [
     // The DATABASE name, as it appears in chado.db.  This also builds the link-out url.  In most cases this will simply be the CV name.  In some cases (EDAM) this will be the SUBONTOLOGY.
     'term_vocabulary' => 'local',
@@ -104,39 +46,30 @@ class local__child_properties extends ChadoField {
     'base_table' => '',
   ];
 
-  // A boolean specifying that users should not be allowed to create
-  // fields and instances of this field type through the UI. Such
-  // fields can only be created programmatically with field_create_field()
-  /**
-   * And field_create_instance().
-   */
   public static $no_ui = FALSE;
-
-  // A boolean specifying that the field will not contain any data. This
-  // should exclude the field from web services or downloads.  An example
-  // could be a quick search field that appears on the page that redirects.
-  /**
-   * The user but otherwise provides no data.
-   */
   public static $no_data = FALSE;
 
   /**
    * @see ChadoField::load()
    **/
   public function load($entity) {
-
-    // ChadoFields automatically load the chado column specified in the
-    // default settings above. If that is all you need then you don't even
-    // need to implement this function. However, if you need to add any
-    // additional data to be used in the display, you should add it here.
     parent::load($entity);
 
     $master = $entity->data__sequence_features['und'];
 
-    //TODO: filter this to just hte properties.  Right now we include everything because we are having this field do double duty for annotations.
-      $entity->local__child_properties['und'] = $master;
+    $properties = [];
+
+    foreach ($master as $child){
 
+      //remove all the other fields from the expand_var.
+      
+      $child['info'] = $child['info']->featureprops;
 
+    }
+
+    //TODO: filter this to just hte properties.
+    // Right now we include everything because we are having this field do double duty for annotations.
+      $entity->local__child_properties['und'] = $master;
 
   }
 
@@ -165,5 +98,4 @@ class local__child_properties extends ChadoField {
       ],
     ];
   }
-
 }