watchexec/crates/events
2023-11-26 03:01:13 +00:00
..
examples --emit-events-to (#515) 2023-03-18 21:32:24 +13:00
src Clippy nursery (#681) 2023-11-26 02:40:57 +00:00
tests Fix some typos (#617) 2023-06-26 22:12:24 +00:00
Cargo.toml Watchexec lib v3 (#601) 2023-11-25 20:33:44 +00:00
CHANGELOG.md Update all changelogs (#682) 2023-11-26 03:01:13 +00:00
README.md Fix and adjust docs (#530) 2023-03-18 10:23:46 +00:00
release.toml --emit-events-to (#515) 2023-03-18 21:32:24 +13:00

watchexec-events

Watchexec's event types.

Fundamentally, events in watchexec have three purposes:

  1. To trigger the launch, restart, or other interruption of a process;
  2. To be filtered upon according to whatever set of criteria is desired;
  3. To carry information about what caused the event, which may be provided to the process.

Outside of Watchexec, this library is particularly useful if you're building a tool that runs under it, and want to easily read its events (with --emit-events-to=json-file and --emit-events-to=json-stdin).

use std::io::{stdin, Result};
use watchexec_events::Event;

fn main() -> Result<()> {
    for line in stdin().lines() {
        let event: Event = serde_json::from_str(&line?)?;
        dbg!(event);
    }

    Ok(())
}

Features

  • serde: enables serde support.
  • notify: use Notify's file event types (default).

If you disable notify, you'll get a leaner dependency tree that's still able to parse the entire events, but isn't type compatible with Notify. In most deserialisation usecases, this is fine, but it's not the default to avoid surprises.