quantumfate / quantumvim Goto Github PK

As a developer/user I want to have a working QuantumVim configuration out of the box. Therefore dependencies should be installed on the system on first time setup should they not be available.

• udate the script to install dependencies
  • detect tools such as nvm for npm

Dependencies:

• ripgrep
• npm
• node

As a user I want to be able to create plugin configurations on the fly that are easily picked up by the runtime logic.

• update genconfic.sh to create a user config plugin scope
• implement a seperate template repository for the configuration
• implement a configuration template for each plugin that provides plugin options, lazy specs and a strategy (#5 ):

General:

local M = {}

-- global options for all user configurations
M.strategy = "override" -- | "keep" | "ignore"
-- these can override the behavior
M.plugin = {}
M.spec = {}

return M

Plugin specific:

local M = {}


-- these can override the behavior
M.plugin = {
    __strategy = "override" -- | "keep" | "ignore"
}
M.spec = {}

return M

As a user/developer I want to be able to inject my configuration into the quantumvim configuration to either disable the full configuration or to extend(force override) existing configuration.

• update functions to load user configuration from files in user config dir
  • base refactoring to module like implementation such as loader (SoC, utility functions)
  • plugins/parents
  • extensions

As a quantumvim user I want to be able to use my personal configuration as well as my own scripts in the runtime path.

• Update bootstrap.lua to reflect necessary rtp modifications
• Update manager.lua to install plugins in the new data directory (decoupling plugin installation from runtime files and user configuration)

• Readme
• badges
• scripts

As a user/developer I want to be able to inject my language specific settings into the present language algorithms without having to make changes in quantumvim's runtime files.

• factor any settings and conditional parameters in the language section out to a confic file (eventually split logically into pieces such as null-ls, lsp and dap in a modular fashion to support future deprecation)
  • dap
  • null-ls
  • lsp
• provide after and ftplugin folder in the user configuration (NOTE: the runtime path for quantumvim's internal ftplugins has to be placed before the ftplugin folder of the user #7 )
• update the template generation
• keep documentation up to date

As a developer I want to have seperate directory for configuration alongside quantumvim.

• add a new variable QUANTUMVIM_RTP_DIR with the new rtp location in ~/.local/state/qvim
• update the scripts to reflect new xdg variables
  • bin
  • install
  • run_test.sh
• update the tests according to the described changes
• update global variables and functions

As a user I want to be able to create user configurations for specific scenarios as well as for different machines. Managing these configurations can be a nuisance when there is no easy way to integrate them into the runtime file.

• update the install script to generate a new user configuration (with a prompt)
• IMPORTANT: update existing user configurations
• a template repository or something else

The configuration should provide various ways to alter the runtime of quantumvim:

• general settings
• plugins
• languages
  • dap
  • lsp
  • null-ls (we use this until there is something new)

As a user I want to have an performing system lol

• do some lazy require on index magic

The code of quantum vim has grown too big so has the amount of log messages. Due to the use of only one logger factory message reports became redundant. Logging an entry at the error level for example causes the message to appear in any sink that is below error as well. Therefor each sink causes an entry to be logged.

• add structlog as a dependency (Has to be in runtime path from the start #7 )
• update the install script to dowload structlog on install in the pack directory
  • ensure lazy can pick up structlog for updates
• implement multiple log factories as logical pieces
• provide multiple log files as logical pieces (eventually seperated in directories, depending on the amount of sinks/factories)

As a developer and user I want a dedicated Log directory that builds on the same logic used to define other logical pieces like config, rtp, etc.

• update the scripts to reflect new xdg variables
  • bin
  • install
  • run_test.sh
• update global variables and functions
• make the changes reflect in structlog
• make the changes reflect in commands and autocommands

Depends on #5

As a user I want to have granular control over the configuration on the user side and the configuration on qvim side.

• implement the logic for the strategies from #9
• implement the strategy pattern to inject user configuration

As a user/developer I want to be able to inject my lazy specs into the quantumvim configuration to either disable the full configuration or to extend(force override) existing configuration.

• update functions to load user configuration from files in user config dir
  • plugins/parents
  • standalone plugins/extensions