Luassert activation keyword may be too sensitive

[carsakiller]

For those using Lunar Vim, it appears they were receiving a popup every time they start a project that asks them if they would like to apply the luassert library LunarVim/LunarVim#3439. Without digging too deep, it seems likely to me that the default config applied by Lunar Vim (when a new workspace is created) adds some libraries that include the assert. keyword, causing it to be suggested every time.

I do not use Lunar Vim - but is someone able to confirm this was the issue? The automatic suggestion of libraries has since been disabled for Lunar Vim LunarVim/LunarVim#3445, but this isn't ideal as now people, by default, will not receive any suggestions. I think a better solution would be to change the keyword to match the require statement for luassert and then that PR can be rolled back.

[carsakiller]

luassert now will only be activated when it detects require("luassert") in a file, rather than assert.

[baggiponte]

Hi! I am using regular nvim with lua-language-server installed via Mason (currently on version 3.6.3) and still experiencing this problem. Could this also be related to a change in the settings/schema necessary to configure the lsp on nvim?

[carsakiller]

Hello @baggiponte, it is likely that some file somewhere has require("luassert"), as did LunarVim. To fix this for LunarVim users, I edited the default configuration so that luassert and busted are enabled by default.

Take a look around for a file that contains require("luassert") and if you find one, that is definitely the problem. Enabling the required libraries, as I did for LunarVim, should fix it 🙂

[baggiponte]

Okay, I found quite a bunch of stuff needed luassert. I simply selected the first option when prompted by the LSP and solved that. Thanks!