Skip to content

Releases: francesca64/hotwatch

v0.5.0

01 Jun 22:55
015ba1c
Compare
Choose a tag to compare

v0.4.6

12 Oct 20:24
66d0d3d
Compare
Choose a tag to compare
  • Removed unnecessary allocation from util::handler_for_event.

v0.4.5

02 Dec 18:47
153ed7d
Compare
Choose a tag to compare
  • The blocking implementation of watch now also accepts FnMut instead of Fn.

v0.4.4

20 Nov 00:14
9e6d36b
Compare
Choose a tag to compare
  • watch now accepts FnMut instead of Fn

v0.4.3

20 Nov 00:14
Compare
Choose a tag to compare
  • Added blocking API.

v0.4.2

13 Jun 00:13
Compare
Choose a tag to compare
  • Re-export notify.
  • Implemented Debug for Hotwatch.
  • Added Hotwatch::new_with_custom_delay.
  • Added Hotwatch::unwatch.
  • The background thread will now stop once Hotwatch is dropped.
  • Updated docs and added an example.
  • Removed dependency on derive_more and parking_lot.

v0.4.1

12 Jun 19:40
Compare
Choose a tag to compare
  • Corrected doc links.

v0.4.0

12 Jun 19:39
Compare
Choose a tag to compare

This release removes the claim of compatability with Rust 1.24, as a patch update to notify changes the minimum requirement to 1.26.

hotwatch 0.3 can still be used with Rust 1.24 if you pin the notify dependency to 4.0.6.

  • Only the latest stable release of Rust is guaranteed to be compatible.
  • hotwatch::Error now implements std::error::Error.

v0.3.1

15 Jun 19:48
Compare
Choose a tag to compare

This release makes hotwatch seem significantly more like a legitimate crate.

  • hotwatch no longer requires nightly Rust! Minimum supported version is 1.24.
  • Uses log instead of obnoxiously using println!.
  • Updated dependencies.
  • Relicensed as dual Apache-2.0/MIT.

v0.3.0

15 Jun 19:47
Compare
Choose a tag to compare

This release includes a non-breaking API change and a potentially breaking behavior change.

  • Hotwatch::watch now accepts any path type that satisfies AsRef<Path>.
  • Paths are automatically canonicalized. This is to prevent surprising behavior with handler matching. As a result of this, the paths enclosed in hotwatch::Event variants are now absolute, which can potentially break existing applications.