It doesn't like my Java datapack files about vscode-bedrock-development-extension HOT 3 CLOSED

Sadly disabling it in a workspace isn't feasible for me :(
Is it out of the question to look for manifest.json to figure out where we are? This naive approach that just looks at a file or folder name causes other issues too, like if you make an entity named blocks.json all the warnings are wrong

from vscode-bedrock-development-extension.

Don't think I can do much in the plugin itself.

You can deactivate the extension for the workspace. Or use the .mcignore file in the root folder to specify what to skip

Example: https://github.com/Blockception/VSCode-Bedrock-Development-Extension/blob/main/.mcignore

from vscode-bedrock-development-extension.

+1

Would be very helpful to only get highlightings, autocompletions, warnings and errors when the behaviour pack or resource pack root folder contains a (valid?) manifest.json file.

Apart from colliding with JE data packs, I noticed the current approach also collides with other plain JSON files. Even when not on a Minecraft context at all.
A while ago I started to have this extention always disabled. Only enabling it when needed and immediately disable it globally again. I hope I dont have too tell you that this is not the way it should works, even so though it works ;)

from vscode-bedrock-development-extension.