search

SoftwareMarbles / lazy

Hackable Coding Assistant
http://getlazy.org
MIT License
1 stars 0 forks source link

Add lazy CLI #9

Open ierceg opened 7 years ago

ierceg commented 7 years ago

Currently we send to lazy only files that users are opening and/or changing in the editor itself. This means that for a user to check all files in a repo they would need to open them one by one in the editor. We should add CLI that could run the analysis on the entire repository.

Question: is monitoring files for changes (in the editor) and sending them all to lazy (respecting .gitignore) desireable? What kind of state would have to be maintained?

ierceg commented 7 years ago

The easiest way to maintain a single core "library" running on client side is to have a CLI compiled binary that is then used from editor plugins. This will guarantee consistent data collection and results.