Added concept of plugins to simplify and generate configuration #2
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR adds the concept of "plugins" to apex.
Goal: To simplify configuration and reduce the amount someone needs to know or change before getting started.
Secondary goal: Support dynamic configurations.
Implementation:
Apex plugins are TypeScript files that export a single default function that has the signature
(doc: apex.Document, config: Configuration) -> Configuration. They take in a parsed apex document with an existing configuration and return a new configuration.For example, given an apex configuration that looks like this:
And where
sample_plugin@v.0.0.0/mod.tslooks like this:Running
generatewould result in configuration that looks like this before getting passed to the generators:Note: The new configuration doesn't need to be dynamic. Plugins are also suitable for turning blobs of configuration into a single plugin definition.