connorgmeehan
commented
1 year ago This is a very very impressive feature set but I'm curious about how adaptable/resistant DUI is to future changes. I'm a bit weary about maintaining another 5000 lines of code as I'm already pretty tight on time. Especially for something like this, unless reliability is 95%+ it might make things harder for the end user (reading docs that have two ways of doing same thing, frustrating when things only work sometimes, crashes cause user to restart neovim). That being said I'm still open to dui, if we can get it in a stable state and if the maintenance cost is low then i'd say it's a good thing to have. I have some questions that might help me understand the maintenance cost of
- How does dui handle new modules, will it automatically show them in the telescope finder?
- How does dui handle changes to the modules API? For example if I renamed
<module_name>.bindsto<module_name>.keybindswhat would need to be updated and in how many places / files? - How resilient is dui to formatting differences, from what I understand it uses treesitter queries, even though we have an auto formatter we should still expect differences in code structure etc. As long as it doesn't crash basically.
- How deeply coupled to the current telescope API is it? If telescope were to change the way you define pickers or handle selecting options what would need to be updated and in how many places? I would prefer to use the most stable version of telescope (as most user's would want that) than run an old version that's compatible with dui.
- Could you also provide a little bit of documentation over the responsibilities of each file in
lua/doom/modules/ui/dui, maybe just 2 lines on what it does and what it interacts with? I'm struggling a bit to understand the architecture.
molleweide
this is just a demo. look at
./modules.lua