How luismateo34/my-nvim works
• Neovim Core: This is the host application that loads the configuration.
• Initialization Module: Represented by files like init.lua and other setup scripts that bootstrap the configuration.
• Lua Configuration Directory: Divide this into subcomponents:
• Plugins: Contains plugin configurations (e.g., ale, telescope, treesitter, vim-dadbod integration, among others).
• LSP: Contains configurations and integrations for the Language Server Protocol. Show that this module communicates with external language servers.
• DAP (Debug Adapter Protocol): Contains per-language debugging configurations (for Golang, JavaScript, PHP, Python).
• Completition: Contains integration scripts for code-completion support with language-specific modules (Blade, PHP, etc.).
• Keymaps: Sets up key bindings for various plugins and editor functions, including maps for LSP, DAP, and telescopic navigation.
• Settings: General editor settings, including snippet configurations (UltiSnips), formatting (prettier), and other custom settings.
• After Queries: This component (located in the “after” directory) provides additional queries—likely used by Tree-sitter or other language analysis tools—for languages like Blade, HTML, and PHP.
• External Dependency: PostgreSQL Client. This external service is essential for the vim-dadbod plugin to interact with databases, and should be represented as an external component that the plugin depends on.
• The Neovim Core loads the Initialization Module (init.lua), which in turn loads the Lua directory and its submodules.
• The Completition and After Queries modules interact; completition scripts may rely on the query scripts (for example, for Blade templates) to provide language-sensitive completions.
• Keymaps and Settings modules influence core behavior by customizing how and when various plugins or functionalities (like testing, debugging, or snippet insertion) are triggered.
Architectural Patterns & Design Principles
• Modular Design: Each aspect of the editor's functionality (snippets, completition, debugging, LSP, key mappings, etc.) is maintained in separate modules, encouraging separation of concerns.
• Extensibility: The clear separation of plugin configurations and external integrations (such as database and language-server support) makes it easy to extend functionality.
• Declarative Configuration: With Lua scripts and organized directories, the design clearly follows a declarative style for editor setup.