You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be smarter and finds the mgit.json file. If the file was not found then goes one level up and tries to find the file once again. After n attempts, it should throw an error - "The configuration file cannot be found." or something like that.
The text was updated successfully, but these errors were encountered:
The cwd option was already removed. Now we need a smarter resolver which scans dir tree up for mgit.json or package.json (once we'll support configuration through package.json).
Feature: Introduced a smarter `cwd` resolver which scans directory tree up in order to find the `mgit.json` file. If the file won't be found, an exception will be thrown. Closes#1.
At this moment, a user can provide the
--cwd
value. This does not make sense.The
cwd
should indicate on the directory which contains the configuration (mgit.json
) file.cwd-resolver
module looks like:It should be smarter and finds the
mgit.json
file. If the file was not found then goes one level up and tries to find the file once again. After n attempts, it should throw an error - "The configuration file cannot be found." or something like that.The text was updated successfully, but these errors were encountered: