mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-06-26 10:54:26 +02:00
Hooks
- Updated documentation and style of example hook scripts.
This commit is contained in:
parent
ec0757b2c9
commit
51291f76fe
4 changed files with 47 additions and 54 deletions
|
@ -3,20 +3,18 @@
|
|||
# The on-add event is triggered separately for each task added
|
||||
|
||||
# Input:
|
||||
# - A line of JSON for the task added
|
||||
read new_task
|
||||
|
||||
# Processing goes here
|
||||
# - line of JSON for the task added
|
||||
|
||||
# Output:
|
||||
# - all emitted JSON lines must be fully-formed tasks
|
||||
# - all emitted non-JSON lines are considered feedback messages
|
||||
echo on-add
|
||||
# - all emitted JSON lines are added/modified as tasks, if the exit code is
|
||||
# zero, otherwise ignored.
|
||||
# - minimal new task: {"description":"Buy milk"}
|
||||
# - to modify a task include complete JSON
|
||||
# - all emitted non-JSON lines are considered feedback messages if the exit
|
||||
# code is zero, otherwise they are considerederrors.
|
||||
|
||||
# Exit:
|
||||
# 0 Means: - all emitted JSON lines are added/modified
|
||||
# - all emitted non-JSON lines become footnote entries
|
||||
# non-0 Means: - all emitted JSON lines are ignored
|
||||
# - all emitted non-JSON lines become error entries
|
||||
read new_task
|
||||
|
||||
echo $new_task
|
||||
echo 'on-add'
|
||||
exit 0
|
||||
|
||||
|
|
|
@ -1,20 +1,20 @@
|
|||
#!/bin/bash
|
||||
|
||||
# The on-exit event is triggered once, after all processing is complete
|
||||
# The on-exit event is triggered once, after all processing is complete, i.e.
|
||||
# last
|
||||
|
||||
# Input:
|
||||
# - A read-only line of JSON for each task added/modified
|
||||
|
||||
# Processing goes here
|
||||
# - read-only line of JSON for each task added/modified
|
||||
|
||||
# Output:
|
||||
# - all emitted non-JSON lines are considered feedback messages
|
||||
# - The onExit event occurs too late to allow any changes, so the input is not
|
||||
# to be modified
|
||||
echo on-exit
|
||||
# - any emitted JSON is ignored
|
||||
# - all emitted non-JSON lines are considered feedback messages if the exit
|
||||
# code is zero, otherwise they are considerederrors.
|
||||
|
||||
# Exit:
|
||||
# 0 Means: - all emitted non-JSON lines become footnote entries
|
||||
# non-0 Means: - all emitted non-JSON lines become error entries
|
||||
while read modified_task
|
||||
do
|
||||
# Scan task
|
||||
done
|
||||
|
||||
echo 'on-exit'
|
||||
exit 0
|
||||
|
||||
|
|
|
@ -1,21 +1,18 @@
|
|||
#!/bin/bash
|
||||
|
||||
# The on-launch event is triggered once, after initialization, before an
|
||||
# processing occurs
|
||||
# The on-launch event is triggered once, after initialization, before any
|
||||
# processing occurs, i.e first
|
||||
|
||||
# No input
|
||||
|
||||
# Processing goes here
|
||||
# Input:
|
||||
# - none
|
||||
|
||||
# Output:
|
||||
# - all emitted JSON lines must be fully-formed tasks
|
||||
# - all emitted non-JSON lines are considered feedback messages
|
||||
echo on-launch
|
||||
# - all emitted JSON lines are added/modified as tasks, if the exit code is
|
||||
# zero, otherwise ignored.
|
||||
# - minimal new task: {"description":"Buy milk"}
|
||||
# - to modify a task include complete JSON
|
||||
# - all emitted non-JSON lines are considered feedback messages if the exit
|
||||
# code is zero, otherwise they are considerederrors.
|
||||
|
||||
# Exit:
|
||||
# 0 Means: - all emitted JSON lines are added/modified
|
||||
# - all emitted non-JSON lines become footnote entries
|
||||
# non-0 Means: - all emitted JSON lines are ignored
|
||||
# - all emitted non-JSON lines become error entries
|
||||
echo 'on-launch'
|
||||
exit 0
|
||||
|
||||
|
|
|
@ -3,22 +3,20 @@
|
|||
# The on-modify event is triggered separately for each task added or modified
|
||||
|
||||
# Input:
|
||||
# - A line of JSON for the original task
|
||||
# - A line of JSON for the modified task
|
||||
# - line of JSON for the original task
|
||||
# - line of JSON for the modified task, the diff being the modification
|
||||
|
||||
# Output:
|
||||
# - all emitted JSON lines are added/modified as tasks, if the exit code is
|
||||
# zero, otherwise ignored.
|
||||
# - minimal new task: {"description":"Buy milk"}
|
||||
# - to modify a task include complete JSON
|
||||
# - all emitted non-JSON lines are considered feedback messages if the exit
|
||||
# code is zero, otherwise they are considerederrors.
|
||||
|
||||
read original_task
|
||||
read modified_task
|
||||
|
||||
# Processing goes here
|
||||
|
||||
# Output:
|
||||
# - all emitted JSON lines must be fully-formed tasks
|
||||
# - all emitted non-JSON lines are considered feedback messages
|
||||
echo on-modify
|
||||
|
||||
# Exit:
|
||||
# 0 Means: - all emitted JSON lines are added/modified
|
||||
# - all emitted non-JSON lines become footnote entries
|
||||
# non-0 Means: - all emitted JSON lines are ignored
|
||||
# - all emitted non-JSON lines become error entries
|
||||
echo $modified_task
|
||||
echo 'on-modify'
|
||||
exit 0
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue