Newbie to VSC: Ability to disable diagnostics on defined globals from another extension?

[Bobertsawesome]

Hello there, forgive me if this has already been asked and answered but I'm not really familiar with VS Code definitions of certain things so I had no luck trying to search for this.

I would like to maintain the Lua Diagnostics setting but immediately upon enabling it, every resource I am working on is tagged as having errors throughout. This is due to the use of many runtime globals that are defined by the game I am coding for: FiveM/RedM. All of these globals (or functions) are defined by another extension I am using.

Is there any way to incorporate or disable the Lua diagnostics for all variables defined by another extension? To manually input these would be impossible as there are thousands.

Example of issue:

[carsakiller]

The ""most correct"" way to resolve this would be to include definition files that show these signatures as being global. Seeing as they already have descriptions and types defined, this could make it easier, as you may be able to copy-paste the definitions from the extension and make sure they are not local.

Another option would be to just add the global signatures to diagnostics.globals. This wouldn't be easy as you would have to manually enter all globals.

Unfortunately, there is no easy way to magically add support for RedM, or its extension. Someone would need to take the time to define everything for use by the language server. However, when that is done, it should make the other extension obsolete, assuming it just provides definitions.