chore: misc doc updates and remove unused exact param from is_in_table

[paulbrittain]

• Misc function doc updates & fixes as I read through code
• Code change:lua/kubectl/utils/find.lua is_in_table() removed unused exact param
• Code change: Set stdin param of vim.system call to nil instead of false - suggested by LSP (May be wrong?)

[mosheavni]

Nice work here thank you. Just fix @Ramilito comments :)

[mosheavni]

also take a look at the type check that is failing:
https://github.com/Ramilito/kubectl.nvim/actions/runs/11249290844/job/31276754598?pr=439

[paulbrittain]

also take a look at the type check that is failing: https://github.com/Ramilito/kubectl.nvim/actions/runs/11249290844/job/31276754598?pr=439

Will do. How do you run the type check locally? :)

[Ramilito]

also take a look at the type check that is failing: https://github.com/Ramilito/kubectl.nvim/actions/runs/11249290844/job/31276754598?pr=439

Will do. How do you run the type check locally? :)

Like this:

luarocks install luacheck
luacheck path/to/your/project

I must warn you that this isn't working 100% for me, I get some errors that are not triggering in my LSP nor in the github-action 😅

[paulbrittain]

@Ramilito Hey Ramilito, yes the local linter doesn't return the same lint errors as the pipeline. Can the linting workflow be enabled so it runs on commits so that I can iterate on resolving the errors it returns commit-by-commit?

Is there a cost incurred per run?

[Ramilito]

@Ramilito Hey Ramilito, yes the local linter doesn't return the same lint errors as the pipeline. Can the linting workflow be enabled so it runs on commits so that I can iterate on resolving the errors it returns commit-by-commit?

Is there a cost incurred per run?

No costs yet so all good, there is a safeguard for all new contributors, probably to avoid denial of service attacks so I had to press a button to allow you to run workflows! Button pressed!

[paulbrittain]

Ready for another workflow run :^)

[Ramilito]

LGTM! Awesome work @paulbrittain, if you are happy with it @mosheavni we can merge it!