Fixes#115
Custom `operatorsFile` configs in .tidyrc were not resolving correctly.
Previously we were using `relative dir operatorsFile`, but if
`operatorsFile` was a relative path (which is the common case), then the
behavior of `relative` is to treat `operatorsFile` as relative to
`cwd` initially (I think it's an error that `relative` is typed as a pure
function). Thus, this only works (reduntantly) if `cwd` is the same as the
`.tidyrc.json` parent directory.
We should be using `resolve [ dir ]` instead to get an absoute path.
With [174928](https://github.com/NixOS/nixpkgs/pull/174928) fully merged
and [upstreamed](https://nixpk.gs/pr-tracker.html?pr=174928) to
`unstable` on Nixpkgs and NixOS, I can confidently say this is
supported. I just tested pulling from unstable and it’s golden.
The way `nodePackages` in `nixpkgs` work, any time anyone updates
anything in the space, all Node pkgs get updated via `node2nix` + a
`generate.sh` script that fetches *all* dependencies. I’m grateful this
project doesn’t have dependencies because `node2nix` is sequential and
resolving ≈ 400 transitive NPM dependencies takes about 4 hours even on
a fast connection. That aside, this pkg will require little to no
maintenance and new versions should come in along with other updates to
`nodePackages`. The only thing that will really matters is that
`purs-tidy` stay compatible with the latest Node LTS.
Unfortunately, it seems I just missed the deadline for `22.05`.
