1. 08 Jun, 2018 1 commit
  2. 27 Mar, 2018 1 commit
    • Eric Putnam's avatar
      (PDOC-228) puppet plans support · da5cad7c
      Eric Putnam authored
      Currently, Puppet Strings only supports Puppet Tasks. Since Plans are
      sort of connected to Tasks, it seemed right that Strings should also
      support Plans. That and Plans are a thing that needs to be documented.
      
      First, the Puppet[:tasks] setting needs to be set to add the 'plan' keyword to the Puppet Parser's lexicon, so this sets it in the Strings parser if the setting exists. If it does not exist and Puppet.version is less than 5.0.0, Strings will error out.
      
      Second, processing for the Plans themselves is set up. Plans are very
      similar to other Puppet objects like defined types and classes, so this
      involved some serious copy-pasta.
      
      Third, all the template/to_hash scaffolding for the different outputs is in place (HTML,
      JSON, Markdown).
      
      Yey.
      da5cad7c
  3. 19 Mar, 2018 1 commit
    • Eric Putnam's avatar
      (PDOC-206) support for Puppet Tasks · 738275b9
      Eric Putnam authored
      Currently, puppet-strings does not know how to generate documentation
      for Puppet Tasks. This does all the work to add support for Tasks
      including a new JSON parser, a task handler, task statement, and task code
      object. Basically, Strings reads the JSON using the native ruby json
      parser and sends values through in a way it understands. It is only
      passing json key/value pairs through, nothing is happening with tags at
      this time. You can now document Tasks and generate HTML, Markdown, or
      JSON output.
      738275b9
  4. 20 Feb, 2018 1 commit
  5. 14 Nov, 2016 3 commits
  6. 11 Oct, 2016 1 commit
    • Will Hopper's avatar
      (PDOC-95) Properly group and display multiple provider `defaultfor`s · a5a3d6b4
      Will Hopper authored
      Prior to this commit, strings did not properly handle providers
      which had multiple related `defaultfor`s. In code, these are written
      as comma-separated constraints. This commit updates strings' puppet
      provider handler, as well as the template which generates HTML for
      `defaultfor` statements.
      
      Note that it was necessary to make a breaking change to the JSON
      schema to accomodate multiple AND'ed defaults. Previously, provider
      defaults were contained in a single key-value map. Now, they are
      contained in an array of key-value lists, which allows multiple
      constraints to be associated with each other.
      a5a3d6b4
  7. 16 Sep, 2016 2 commits