Open e-dant opened 1 year ago
The messaging syntax (including errors) should be detailed in the readme.
Messages come through event. The where field looks like this:
event
where
[s, e]/[sys, self]/[description]
Where s means "successful" (such as s/self/live@path) and e means "error" (such as e/sys/read).
s
s/self/live@path
e
e/sys/read
self means we failed. sys means the operating system failed.
self
sys
The description is usually a function name, an api, or a path. It's something extra.
description
These events always have the kind field as watcher (as opposed to file, dir, etc).
kind
watcher
file
dir
The what field varies. When a watcher first starts watching, what is create. When a watcher dies, it's destroy. Error messages are usually other.
what
create
destroy
other
We need to put this in the readme.
This could go in the "The Library" section of the readme.
Can't think of a better first issue for potential contributors to get their name up on the project!
The messaging syntax (including errors) should be detailed in the readme.
Messages come through
event
. Thewhere
field looks like this:[s, e]/[sys, self]/[description]
Where
s
means "successful" (such ass/self/live@path
) ande
means "error" (such ase/sys/read
).self
means we failed.sys
means the operating system failed.The
description
is usually a function name, an api, or a path. It's something extra.These events always have the
kind
field aswatcher
(as opposed tofile
,dir
, etc).The
what
field varies. When a watcher first starts watching,what
iscreate
. When a watcher dies, it'sdestroy
. Error messages are usuallyother
.We need to put this in the readme.