dat automatically finds <dat.json>

If I type dat . or dat clone dat.json or dat clone . in a directory that has a dat.json file, it should use the url key in the file. This is nice for github repos so I just add the hash once in the dat.json file and forget about it.

[TimothyStiles]

It looks like the default behavior for dat clone . when there’s already a .dat folder is to listen for updates. I’m just going to leave that be.

[TimothyStiles]

@joehand I’ve put together a pull request that checks for and parses dat clone . and dat clone path/to/dat.json that I haven’t submitted yet.

dat clone . and dat clone dat.json both clone the content of the dat repo directly into the current working directory without a fourth dir argument.

dat clone path/to/dat.json without a dir argument makes a new directory named after the key link which contains the dat repo.

dat clone path/to/dat.json dir works as expected.

I’ve only tried this with empty directories with a single dat.json file in it. It looks like I should also write something that throws an error if there’s already a .dat folder within the target directory. Should I make that as a second pull request or roll that into the one I’m about to make?

Also, I can’t key pass clone a null value such as dat clone. I think it has something to do with src/parse-args.js. I tried writing a test using the clone - default ops as a template but I’ve been running into trouble.