Skip to content

Releases: braincore/ifft

v0.11

17 Oct 06:15
Compare
Choose a tag to compare
  • Add restart_on for delegates to trigger process restart.
  • Make non-verbose mode quieter.

v0.10

26 Apr 09:13
Compare
Choose a tag to compare

Flag -V prints out version number.

v0.9

26 Apr 09:05
Compare
Choose a tag to compare

Add support for delegation.

v0.8

02 Feb 03:10
Compare
Choose a tag to compare
  • Support ignore files.
  • Improved watch reliability with large trees.

v0.7

20 Mar 00:20
Compare
Choose a tag to compare
  • Add support for dependencies via listen & emit options.
  • Add support for omitting watch path or using current dir ".".

v0.6

09 Sep 05:34
Compare
Choose a tag to compare
  • Add desktop notifications (toggled with -n flag).
  • Fix flood of file events hanging ifft.

v0.5

08 Aug 10:29
Compare
Choose a tag to compare

Add support for canonicalizing paths with symlink components.

v0.4.1

12 May 19:02
Compare
Choose a tag to compare

Bug fix. 0.4 is broken due to a premature watcher de-allocation.

v0.4

12 May 18:55
Compare
Choose a tag to compare

Add -q (quit after run) flag.

Useful for running one-off operations on the tree without having to listen for changes after. Can be used for creating a production build or for running a clean on the directory tree.

To make this work, an ifft without an if-cond now triggers on nothing, rather than everything.

v0.3

12 May 18:10
Compare
Choose a tag to compare

Previously, ifft has had a monolithic config file that would specify the root folder to watch and all the triggers for the entire directory tree. It's now moving to a decentralized model.

The root folder is not specified in any config file. The root folder is passed to the ifft command. ifft then traverses the directory looking for all ifft.toml config files. This allows each sub-project to better manage their own trigger needs.

In addition, support for -r (run-before) has been added. This automatically triggers ifft rules on start without waiting for a file event. This is important for build systems where you don't want to wait for a file change to initiate the first build.