refactoring, cleaning up, removing gitmodules for now

TODO.md

@@ -19,7 +19,7 @@
       instead of having it under `[module].config` - [ ] If necessary, then make inter-module config accessibility under `[module].config` instead of `module.config`
 - [ ] (easy) Change config to be under
 - [ ] (easy) Consider removing `[module].load` `[module].maps` `[module].opts` `[module].cmds` and merge all into `[module].setup` due to redundancy
-- [ ] (easy) Remove all lingering instances of `[module].data.data` and merge into `[module].data`
+- [ ] (easy) Remove all lingering instances of `[module]..` and merge into `[module].`
   - [ ] (easy) Consider another separation of tables and functions of a module
 - [ ] (easy) Fix `ui.calendar` for `note` module
 - [ ] (easy) Fix mod popup window buffer close error

book/lua/module/examples/barebones.lua

@@ -1,18 +1,15 @@
 ---@brief Let's go through the most boilerplate, simple example of a module you may use.
 ---@brief This module will have no real functionality,
-local mod = require "down.mod"
-
+local mod = require 'down.mod'
 
 ---@brief Let's say you want to create a module for Jupyter notebooks to run in Neovim.
 ---@brief We'll start by just creating a barebones module, with no functionality, just to show you how.
 ---@brief We will name this module "jupyter".
 ---@type down.Mod
-local J = mod.create("jupyter", {
-
-  ---@brief This is where we would automatically call any submodules underneath "jupyter" to be called in
-  ---@brief simultaneously as it is loaded. Since we do not have any such submodules, we will leave this empty.
+local J = mod.new 'jupyter'
 
-})
+---@brief This is where we would automatically call any submodules underneath "jupyter" to be called in
+---@brief simultaneously as it is loaded. Since we do not have any such submodules, we will leave this empty.
 
 --[[           1. Flow of functions:
 
@@ -37,39 +34,33 @@ function J.setup()
     ---@brief through in such an early stage. Taking a guess, however, and knowing we can always change,
     ---@brief we'll just choose a few which we will likely need regardless.
     requires = {
-      "data",
-      "workspace",
-      "data.code",
-      "ui.progress",
-      "ui.status",
-      "ui.notify",
-      "ui.vtext"
-    }
+      'data',
+      'workspace',
+      'data.code',
+      'ui.progress',
+      'ui.status',
+      'ui.notify',
+      'ui.vtext',
+    },
   }
 end
 
 ---@brief This is where we will set up the module's data and any methods it will call.
 ---@class down.jupyter.Data
-J.data = {
-
-  ---@brief One such piece of data you may wish to store is the ongoing collection of cells, as well
-  ---@brief as their contents and type in the Juypyter notebook. You may even wish to leverage the
-  ---@brief down.lua `lsp.notebook` module to hook into the LSP for Jupyter notebooks.
-  cells = {
-
-  },
-
-  ---@brief To keep track of the notebook currently being interacted with
-  notebook = {
 
-    path = nil,
+---@brief One such piece of data you may wish to store is the ongoing collection of cells, as well
+---@brief as their contents and type in the Juypyter notebook. You may even wish to leverage the
+---@brief down.lua `lsp.notebook` module to hook into the LSP for Jupyter notebooks.
+J.cells = {}
 
-    name = nil,
+---@brief To keep track of the notebook currently being interacted with
+J.notebook = {
 
-    kernel = "python3",
+  path = nil,
 
-  }
+  name = nil,
 
+  kernel = 'python3',
 }
 
 ---@brief Technically, we have now created a proper module that can be loaded into Neovim through down.lua.
@@ -92,27 +83,25 @@ J.config = {
   ---@brief consider that a user will likely want to change several of the values.
   notebook = {
 
-    default = "notebook.ipynb",
+    default = 'notebook.ipynb',
 
     dir = {
 
-      workspace = "default",
-
-      default = "notes",
-    }
+      workspace = 'default',
 
+      default = 'notes',
+    },
   },
 
-  service = "jupyter",
+  service = 'jupyter',
 
-  command = "jupyterlab",
+  command = 'jupyterlab',
 
-  kernel = "python3",
+  kernel = 'python3',
 
   kernels = {
-    "python3"
-  }
-
+    'python3',
+  },
 }
 
 ---@brief There are many more aspects to a module that can and should be defined as you begin to flesh it out,

book/lua/module/examples/basic.lua

@@ -44,7 +44,7 @@ M.config = {
 }
 
 ---@class example.Data
-M.data = {
+M. = {
   --- @brief module data
   ---          the home of the module's internal data and methods
   ---          TODO: split up concerns

book/src/modules/examples.md

@@ -56,17 +56,16 @@ end
 
 ---@brief This is where we will set up the module's data and any methods it will call.
 ---@class down.jupyter.Data
-J.data = {
 
   ---@brief One such piece of data you may wish to store is the ongoing collection of cells, as well
   ---@brief as their contents and type in the Juypyter notebook. You may even wish to leverage the
   ---@brief down.lua `lsp.notebook` module to hook into the LSP for Jupyter notebooks.
-  cells = {
+  J.cells = {
 
-  },
+  }
 
   ---@brief To keep track of the notebook currently being interacted with
-  notebook = {
+  J.notebook = {
 
     path = nil,
 
@@ -76,7 +75,6 @@ J.data = {
 
   }
 
-}
 
 ---@brief Technically, we have now created a proper module that can be loaded into Neovim through down.lua.
 ---@brief However, we will be typically be best off at the beginning characterizing the module with any
@@ -175,14 +173,6 @@ M.config = {
   --- ...
 }
 
----@class example.Data
-M.data = {
-  --- @brief module data
-  ---          the home of the module's internal data and methods
-  ---          TODO: split up concerns
-  --- ...
-}
-
 M.load = function()
   --- @brief module load
   ---          a set of functions to run whenever the

book/src/modules/index.md

@@ -42,13 +42,6 @@ M.config = {
   --- ...
 }
 
----@class example.Data
-M.data = {
-  --- @brief module data
-  ---          the home of the module's internal data and methods
-  ---          TODO: split up concerns
-  --- ...
-}
 
 M.load = function()
   --- @brief module load
@@ -61,4 +54,3 @@ end
 return M
 
 ```
-

lua/down.lua

@@ -39,18 +39,44 @@ function Down:start()
   for name, usermod in pairs(self.config.user) do
     if type(usermod) == 'table' then
       if name == 'lsp' and self.config.dev == false then
-        goto continue
+      elseif name == 'log' then
+        if type(usermod) == 'table' then
+          Down.config.log = usermod
+        elseif type(usermod) == 'number' and usermod >= 0 and usermod <= 4 then
+          Down.config.log.level = Down.util.log.number_level[usermod] or 'info'
+        elseif type(usermod) == 'boolean' then
+          Down.config.log.level = 'info'
+        elseif type(usermod) == 'string' then
+          if
+              usermod == 'trace'
+              or usermod == 'debug'
+              or usermod == 'info'
+              or usermod == 'warn'
+              or usermod == 'error'
+              or usermod == 'fatal'
+          then
+            Down.config.log.level = usermod
+          end
+        end
       elseif name == 'workspaces' then
-        goto continue
       elseif name == 'workspace' then
-        goto continue
       elseif self.mod.load_mod(name, usermod) == nil then
       end
     else
       self.config[name] = usermod
     end
-    ::continue::
   end
+  vim.api.nvim_create_autocmd('BufEnter',
+    {
+      callback = function()
+        for _, l in pairs(Down.mod.mods) do
+          Down.mod.load_maps(l)
+          Down.mod.load_opts(l)
+        end
+      end,
+      pattern = "markdown",
+    }
+  )
   self.config.mod = self.mod.mods
   self.config:post_load()
   self:post_load()