You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To go along with #14, once we have optional labels for the steps in a config file, we should be able to allow preset configurations of them. For instance:
If this goes in the config file, we need to add a actions: block level or something to differentiate. Right now the whole file's top level is an array; that will need to be subordinated to actions: the way those above are subordinate to routines:. Can probably allow the current format, conditionally, as long as there are no routines declared.
Also, routines may require a way to handle build-steps, which is probably most of what we'd want to filter. If they're named, we can list them as sub-steps of their parent using publish-book:pdf.
routines:
- name: no-pdfskip:
- publish-book:pdf
The text was updated successfully, but these errors were encountered:
To go along with #14, once we have optional labels for the steps in a config file, we should be able to allow preset configurations of them. For instance:
If this goes in the config file, we need to add a
actions:
block level or something to differentiate. Right now the whole file's top level is an array; that will need to be subordinated toactions:
the way those above are subordinate toroutines:
. Can probably allow the current format, conditionally, as long as there are no routines declared.Routines could be called from the command line:
bundle exec liquidoc -c _configs/build.yml -r jekyll-only
Also, routines may require a way to handle build-steps, which is probably most of what we'd want to filter. If they're named, we can list them as sub-steps of their parent using
publish-book:pdf
.The text was updated successfully, but these errors were encountered: