These are some of the things to be completed for autodot (some of these require further discussion):
- [Discuss] Add an
uninstall
field toautodot.json
which let's users uninstall dotfiles. - [Discuss] Consider a global
autodot.json
file that allows one to access things like commands from thescripts
section from anywhere. - [Discuss] Consider making it possible to use autodot commands (or only autodot scripts) from anywhere, and not just the dotfiles directory that uses autodot. User might have to specify the directory containing
autodot.json
, since multiple such directories can exist. - Assuming 3 is completed, allow users to give names to directories containing
autodot.json
files (like an alias), so that it is easy to invoke commands from various directories without having to remember their paths. - A backup feature (implemented using an optional
backup
field inautodot.json
with a default fallback) that allows one to backup their dotfiles, perhaps before installing new dotfiles. - Assuming 5 is completed, add a flag to the
autodot install
command that automatically backs up existing dotfiles before installing new ones, using thebackup
command from 5. - Assuming 5 is completed, a complementary
restore
command may also be added to restore the backed up dotfiles.
- Add default scripts for
bootstrap
andsync
commands as fallbacks for when theautodot.json
file has no value for the corresponding commands - Add a flag to the
bootstrap
andsync
commands to allow the invocation of default scripts (this assumes that 1 has been approved and completed) - [Important] Add tests for all the commands and mandate the writing of tests for new functionality.
- Consider adding multiple defaults (see point 1) for each command, each default having a different (standard) approach to achieving it's purpose.
- Integrate code coverage reports (assumes that tests have been added in accordance with point 4 of the code section).
- [Important] Decide upon the major goals, milestones and functionality for the release of autodot v1.0.0.