Extension ignores settings and mcproject files like .mcignore, .mcdefinitions and .mcattributes about vscode-bedrock-development-extension HOT 18 OPEN

Oh, okay thanks for trying 👍 Were you able to reproduce the UI schema issues on your end? Is that a result of incomplete schema or something else?

Think I really really fixed it now, version 7.0.4 is uploading

from vscode-bedrock-development-extension.

If its a thing about json structure, I cannot do anything

from vscode-bedrock-development-extension.

Has the UI thing been resolved? It should be just packaged within the extension. Might indicate an extension that's corrupted.
Possibly best to remove that extension, and the folder in the .vscode

from vscode-bedrock-development-extension.

For the .mcignore not working, I'm wondering something.

It might be that a top-level project is loading in everything. The plugin doesn't support Minecraft project files in subfolders atm.

So each workspace might be working as intended but an upper level level workspace is loading all

from vscode-bedrock-development-extension.

Has the UI thing been resolved? It should be just packaged within the extension. Might indicate an extension that's corrupted. Possibly best to remove that extension, and the folder in the .vscode

Tried uninstalling all bedrock-related extensions and deleting any traces from that folder. On re-install the issue still persist unfortunately. Can you check if the schemas in the latest extension have the 'CAE_variables' being referenced by the error (last screenshot).

So each workspace might be working as intended but an upper level level workspace is loading all

I think this is probably the case. That top root folder named 'Bedrock Library' in Screenshot#1 has a bunch of addons in various subfolders. Is there a way to keep that in my workspace but make the extension ignore it? (would like to keep it for easy reference).

Additionally, let me know if there's any test or logging you would like me to run on my workspace to diagnose this. If projects in subfolders are the issue, would you consider adding support for that in future? Or maybe just a way to ignore it.

I will test my workspace with root folders added and removed and let you know if anything changes.

from vscode-bedrock-development-extension.

Think to stop the root folder from checking all, you would have to add a pattern to the .mcignore of the root to not go deeper

from vscode-bedrock-development-extension.

Tried uninstalling all bedrock-related extensions and deleting any traces from that folder. On re-install the issue still persist unfortunately. Can you check if the schemas in the latest extension have the 'CAE_variables' being referenced by the error (last screenshot).

Think I have fixed this

from vscode-bedrock-development-extension.

Sorry, but the UI schema issue still exists in version 7.0.3.

Additionally, I tried removing every root folder in my workspace except one, and it has zero addons in subdirectories, it's just the vanilla BP from Microsoft. And .mcignore files still don't work in this setup :(

from vscode-bedrock-development-extension.

I tried again, opening a completely new window, adding just the vanilla BP folder with the .mcignore file and even this doesn't work. It's not even a saved workspace, just a new window with nothing but the vanilla BP opened. The extension just refuses to respect .mcignore files at all. Should be very easy to reproduce.

from vscode-bedrock-development-extension.

A more comprehensive video with voice-over providing as much context as possible:
https://www.youtube.com/watch?v=HTfvEtjTUQs

Hope this helps :)

from vscode-bedrock-development-extension.

Sorry, but the UI schema issue still exists in version 7.0.3.

Additionally, I tried removing every root folder in my workspace except one, and it has zero addons in subdirectories, it's just the vanilla BP from Microsoft. And .mcignore files still don't work in this setup :(

That errors, which is a json errors. Cannot be ignored through mcignore, its just a thing vscode does

from vscode-bedrock-development-extension.

That errors, which is a json errors. Cannot be ignored through mcignore, its just a thing vscode does

No, because that is valid JSON syntax. Also, the errors go away when the extension is disabled.

from vscode-bedrock-development-extension.

That errors, which is a json errors. Cannot be ignored through mcignore, its just a thing vscode does

No, because that is valid JSON syntax. Also, the errors go away when the extension is disabled.

2023-11-02.01-35-21.1.mp4

Doesn't matter the extension cannot ignore json through mcignore

from vscode-bedrock-development-extension.

Doesn't matter the extension cannot ignore json through mcignore

Yeah, I was referring to the part where you said it's just a thing VS code does.
Can this be disabled through extension settings then?

from vscode-bedrock-development-extension.

Doesn't matter the extension cannot ignore json through mcignore

Yeah, I was referring to the part where you said it's just a thing VS code does. Can this be disabled through extension settings then?

Also no sadly, vscode would require a couple more features

from vscode-bedrock-development-extension.

Oh, okay thanks for trying 👍
Were you able to reproduce the UI schema issues on your end? Is that a result of incomplete schema or something else?

from vscode-bedrock-development-extension.

So CAE_Variables is fixed but now this shows:

From what I recall there were only like a handful of missing definitions, so fixing it shouldn't be too difficult I hope. 🤞

from vscode-bedrock-development-extension.

Hey, just got back to working on addons and noticed the UI errors have gone away. Nice!
Have we concluded that there's nothing we can change about how the extension highlights schema mismatches in files tracked by .mcignore? Even when all diagnostics are disabled in extension settings?

from vscode-bedrock-development-extension.