- create POC
- decide on API
- make it work for my own config
- support for commits and tags
- support for running commands after clone
- support tables with options in from (+tests)
- write initial setup routine
- update images to have git configured properly (name email)
- use sub module instead of clone
- clone plugins into opt and call
packadd
in .from
- display some UI during clone
- create basic API for lazy-loading on events
- add example using Kickstart as a base
- write tests for to_handle
- add commands
-
:Baggage
to open a split of terminal and docs in a new tab with guidance on how to use git to update plugins
-
- add way for examples to use cached plugins to speed up debugging
- watcher for example runner
- let it sit for a while
- do a code review, refactor
- create basic API for lazy-loading on key presses
- provide example for lazy-loading
- on events
- on key press
- add docs/help
- write proper readme
- include version number in plugin-path if set
- create a cli to handle updates etc
- automated tests using the examples?
- support for a
dependency
property? I usually found that order of imports is much more intuitive. However including it would make the migration path from something like lazy a bit easier, since it would include less changes.
And tasks that turned out not work or decided shouldn't be part of baggage.
- A fancy UI
Instead of a UI, make it easy to run the appropriate git commands that will give similar results and has far greater value
-
[-] vim.g.baggage_* to vim.g.baggage.* for LSP? Not worth it, because one would have to check if vim.g.baggage exists in the install script
-
[-] add keymap tracker to prevent duplicate keymaps