Resolve absolute path to operatorsFile #117
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #115
Custom
operatorsFile
configs in .tidyrc were not resolving correctly. Previously we were usingrelative dir operatorsFile
, but ifoperatorsFile
was a relative path (which is the common case), then the behavior ofrelative
is to treatoperatorsFile
as relative tocwd
initially (I think it's an error thatrelative
is typed as a pure function). Thus, this only works (reduntantly) ifcwd
is the same as the.tidyrc.json
parent directory.We should be using
resolve [ dir ]
instead to get an absoute path.