Run a ZiftScript to create the ZiftSetup, and then use ziftWithSetup

ziftWith = renderZiftSetup >=> ziftWithSetup

Build a zifter using a ZiftSetup.

A zifter has the capabilities that you would expect from a 'zift.hs' file:

• zift.hs run: Run the zift.hs script as a pre-commit hook.
• zift.hs preprocess: Run the preprocessor
• zift.hs precheck: Run the prechecker
• zift.hs check: Run the checker
• zift.hs install: Install the zift.hs script as a pre-commit hook.

Add a given zift action as a preprocessor.

Add a given zift action as a prechecker.

Add a given zift action as a checker.

Declare a given list of Zift actions to be execute in parallel.

Like mapA, but specialised to Zift and '[]', and ensures that the output of actions is printed in the right order, even if they are executed in an arbitrary order.

Like mapA_, but specialised to Zift and '[]', and ensures that the output of actions is printed in the right order, even if they are executed in an arbitrary order.

Like for, but specialised to Zift and '[]', and ensures that the output of actions is printed in the right order, even if they are executed in an arbitrary order.

Like for_, but specialised to Zift and '[]', and ensures that the output of actions is printed in the right order.

Recursively call each zift.hs script in the directories below the directory of the currently executing zift.hs script.

Only the topmost zift.hs script in each directory is executed. This means that, to execute all zift.hs scripts recursively, each of those zift.hs scripts must also have a recursiveZift declaration.

Get the root directory of the zift.hs script that is being executed.

Get the temporary directory of the zift.hs script that is being executed.

To persist any state between runs, use this directory.

Get all the Settings

Get a single setting

Print a message (with a newline appended to the end).

Print a message (with a newline appended to the end), in the standard zift script color. This is the function that the zift script uses to output information about the stages of the zift script run.

Print a message (with a newline appended to the end) that signifies that a part of the processing is now done.

Example:

doThingZift :: Zift ()
doThingZift = do
    doThing
    printProcessingDone "doThing completed successfully."

Print a message (with a newline appended to the end) that signifies that a part of the processing failed. This message will not cause the zift script run to fail.

Example:

doDangerousThing :: Zift ()
doDangerousThing = do
    errOrResult <- doThing
    case errOrResult of
        Left err ->
            printPreprocessingError $
                unwords ["doThing failed with error:", err]
            fail "doThing failed."
        Right result -> do
            printPreprocessingDone
                unwords ["doThing succeeded with result:", result]

Print a message (with a newline appended to the end) with custom colors.

See the ansi-terminal package for more details.