Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning setting up kickstart in init.lua #1257

Closed
forevpurity opened this issue Dec 8, 2024 · 4 comments
Closed

Warning setting up kickstart in init.lua #1257

forevpurity opened this issue Dec 8, 2024 · 4 comments

Comments

@forevpurity
Copy link

Hi,

I'm new to nvim, after following the installation guide, when I opened init.lua, there're a lot of warnings, is this normal, or did I do something wrong, I'm using Ubuntu-24.04 on WSL:

image
image

Thanks a lot for help !!!

@r-keenan
Copy link

r-keenan commented Dec 8, 2024

Yeah, I am having the same issue. I will let you know if I figure out the fix. I have not had an opportunity to troubleshoot it.

@iton0
Copy link
Contributor

iton0 commented Dec 8, 2024

uncomment this line your code
-- diagnostics = { disable = { 'missing-fields' } },

@feoh
Copy link
Collaborator

feoh commented Dec 12, 2024

Hi.

Missing field detection is a feature that, as @iton0 pointed out, can be disabled.

Working as designed. Closing.

@paatre
Copy link

paatre commented Jan 4, 2025

Wanted to add a comment here to reiterate what @iton0 suggested here to use the missing-fields warning disabling. I noticed that @Ln86 reacted with a 👎🏻 emoji so maybe this helps: an issue has been created on the mason-lspconfig repository 3 weeks ago that also describes this exactly the same warning issue: williamboman/mason-lspconfig.nvim#500.

The issue author notes the following in the comment section:

Use ---@diagnostic disable [missing-fields] or pass all the MasonLspconfigSettings fields to the setup call until this is addressed.

mason-lspconfig is only one Lua plugin with "missing required fields" that lua_ls warns about. It wouldn't be wise from Kickstart's point of view to start addressing all the different plugin definition issues that rise up. It isn't Kickstart's job, it's for the plugin contributors to keep the type annotations as such that reflects the reality of how the configuration should and can be used. In this required fields case, the plugin contributors can make the fields optional which fixes these warning issues.

But, if a single Neovim (especially with a Kickstart variant on this context) user wants to address this issue without disabling the warning, you can provide some defaults by yourself.

Hopefully this helped!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants