Skip to content

Latest commit

 

History

History
95 lines (56 loc) · 1.89 KB

ROADMAP.md

File metadata and controls

95 lines (56 loc) · 1.89 KB

ROADMAP

0.0.0 poc

  • create poc
  • decide on API
  • make it work for my own config
  • support for commits and tags

0.1.0 making it usable

  • 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 submodule instead of clone
  • clone plugins into opt and call packadd in .from

0.2.0 vertical slice

  • 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

0.3.0 conveniences

  • add commands

0.4.0 examples

  • add way for examples to use cached plugins to speed up debugging
  • watcher for example runner

0.5.0 let it simmer

  • let it sit for a few days

0.6.0 brush up

  • do a code review, refactor

0.7.0 utilities

  • create basic api for lazy-loading on keypresses
  • add keymap tracker to prevent duplicate keymaps
  • provide example for lazy-loading
    • on events
    • on keypress

0.8.0

  • add docs/help

1.0.0

  • write proper readme

brainfarts

  • include version number in plugin-path if set

Unsure

  • 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 incloud less changes.

Won't implemenent

and tasks that turned out not work

  • 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