Releases: DocOps/liquidoc-gem
LiquiDoc v0.12.0
This release introduces lots of new filters (see LiquiDoc Liquid Filters API Reference).
LiquiDoc now also ingests data from AsciiDoc documents (attributes).
Liquidoc 0.12.0.pre.rc1
0.12.0-rc1 Add script for automating gem release
LiquiDoc 0.11.0
Major: Enables complex data objects ingested from multiple source files.
Minor: Moves docs to proper arrangement, moving all but the essentials out of README.
LiquiDoc 0.10.0
The 10th minor release of LiquiDoc introduces a new type of action called execute
, which allows users to invoke arbitrary shell commands from within a LiquiDoc routine.
It also properly prepares and instructs dependent gem management and cleans up some text in the README.
LiquiDoc 0.9.5
This patch enhances the migrate action.
The options:
setting for migrate
actions was reading an erroneous truthiness to test for the existence of a setting.
Fixed this so opt settings other than inclusive: false
actually work.
Added the ability to set an option missing:
with either warn
or raise
as values.
missing: warn
: the operation skips the migrate step and logs a warning to console.missing: skip
: the operation skips, only warning under--verbose
.missing: exit
(default, backward compatible): the operation throws an error and exits.
Added example and explanation for new missing:
setting to README and improved the illustrative capacity of the examples.
Thanks for help from Hector Palacios (@hpalacio).
LiquiDoc 0.9.4
This patch release makes two significant changes:
-
PDFs are now built using the asciidoctor-pdf gem, allowing unlimited attribute ingest.
-
Recursive copying makes the proper paths when traversing multiple directory levels.
LiquiDoc 0.9.3
This patch addresses problems caused by passing certain Jekyll arguments over the command line when using dynamic configs introduced in 0.9.0.
-
Properly trigger dynamic config build
Based on:- explicit --parse-config flag
- passing of any --var during a config build
- existence of Liquid tags in config file
-
Add Liquid detection proc; returns true if Liquid tags found
-
Stop passing Jekyll config params over CLI
Pass config-based Jekyll arguments to jekyll as a Jekyll config file instead of over CLI
LiquiDoc 0.9.2
Fixes a bug introduced in the previous patch that was overzealously forcing an empty hash even when a valid one existed.
LiquiDoc 0.9.1
This maintenance release:
- recuperates code lost in a bad merge reconciliation, restoring Algolia functionality removed during bad rebase
- fixes a bug that inhibiting adding variables to an empty set
LiquiDoc 0.9.0
This release adds some significant features.
CLI Parsing with Environment Variables
Adds a --var option for CLI-only parse builds, so environment variables can be passed via the command line. Previously, parse builds run from the command line with no config file could only rely on a data file for variable ingest. Now, Liquid templates can expect a variable to be passed into the vars.
scope from the command line by adding --var varname=varval
, where varname
is your variable's key and varval
is the assigned value. This may be repeated until you run out of room on the command line.
Dynamic Configuration
Configuration files can now be formatted in Liquid and preprocessed before being run as the build routine. The procedure:
- runs a conventional LiquiDoc parse action on the chosen config file;
- saves a parsed version to
<build_dir>/pre/
; then - proceeds running the
liquidoc
command using the new ephemeral config.
Algolia Search Integration
LiquiDoc will now push built HTML files to Algolia indexes. If you're an Algolia user with a complex Jekyll build, this wrapper may be of some assistance. It's really just a gateway to make pushing to Algolia's index with its own Jekyll plugin a little easier.