Pure decisions of the watcher: when a change is settled enough to compile, and whether a report is news.
Pure decisions of the watcher: when a change is settled enough to compile, and whether a report is news.
(decide memory report)Is report news, given the memory of the previous one (nil at first)?
A failure is news when it differs from the last one. The same failure seen again is not: a save that fixes nothing must not repeat the message. A clean build is news only right after a failure.
Is `report` news, given the `memory` of the previous one (nil at first)? A failure is news when it differs from the last one. The same failure seen again is not: a save that fixes nothing must not repeat the message. A clean build is news only right after a failure.
(memory-of report)What to remember of report for the next decide.
What to remember of `report` for the next `decide`.
(notice-of root report decision)The Notice decision calls for, or nil for a quiet one.
The Notice `decision` calls for, or nil for a quiet one.
(step {:keys [seen pending changed-at] :as state} stamps now debounce-ms)Advance the debounce state with a fresh stamps sample taken at now.
Returns [state compile?].
A change is compiled once the same stamps have been seen for
debounce-ms: an editor that writes several files in a burst triggers
one build, not one per file. The first sample is itself a change, so a
watcher reports the state of the build it was started on.
Advance the debounce state with a fresh `stamps` sample taken at `now`. Returns `[state compile?]`. A change is compiled once the same stamps have been seen for `debounce-ms`: an editor that writes several files in a burst triggers one build, not one per file. The first sample is itself a change, so a watcher reports the state of the build it was started on.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |