formerlatter.txt

Former and latter fun!

 * It is up to the class implementing this interface to manage where the
 * information comes from. For example, field.module provides an implementation
 * based on two levels of configuration. It allows the site administrator to add
 * custom fields to any entity type and bundle via the "field_config" and
 * "field_instance_config" configuration entities. The former for storing
 * configuration that is independent of which entity type and bundle the field
 * is added to, and the latter for storing configuration that is specific to the
 * entity type and bundle.
 
 'former' options
 
 1. "field_config"
 2. custom fields
 3. any entity type and bundle via the "field_config"
 4. custom fields to any entity type and bundle via the "field_config"
 5. custom fields to any entity type and bundle via the "field_config"...configuration entities
 
 'latter' options
 
 1. "field_instance_config"
 2. custom fields
 3. any entity type and bundle via the...""field_instance_config"
 4. custom fields to any entity type and bundle via the...""field_instance_config"
 5. custom fields to any entity type and bundle via the...""field_instance_config"...configuration entities