YAML setting breaks extension

[jerone]

Since a few versions ago, Maestro Workbench is forcing a YAML setting in our workspace settings. Introduced in #68
As the setting is user depended, this is creating an issue for other users in the workspace.
Plus, we just had Maestro Workbench fail because of an update to version 0.9.4, while the setting is hardcoded to version 0.9.3.

Why is this setting forced upon us and why is it hardcoded to the user and why is it hardcoded to a specific extension version?

[Mastersam07]

I see what is going on here.

• fix: workspace settings #68 is a controversial but a better solution is in the works.

For the questions asked,

• Test settings are usually different per project(different folder and file patterns) hence we moved the workspace configuration to the user's workspace.
• The setting isn't exactly hardcoded. On updating, the extension tries to remove old references and update its references to the latest version(which finds its path on the user local machine).
• Since the extension path carries the path on user's local machine and extension version, this could cause failures especially if same configuration is used on a different machine for same project. (I believe this is your case?)

For a quick fix, editing and saving the file patterns should cause workbench to update its configuration.

[jerone]

For a quick fix, editing and saving the file patterns should cause workbench to update its configuration.

Changing the path in de setting to 0.9.4 did indeed fix the issue.

I'm not sure what to do with this now; do we still need this setting? I cannot find any documentation about this setting in the readme.
Moving this setting to the workspace is also not possible, as it's user depended. But I also don't want to have to update the version after every release for all my team-members separately.

[Mastersam07]

A more permanent fix is being worked on @jerone .

[TsTeamDev]

Hi,
I have 0.9.4 version and I am still getting the same error:
Unable to load schema from '/Users/user1/.vscode/extensions/mastersam.maestro-workbench-0.9.3/schema/schema.v0.json': No content.
I was able to fix it by updating the path in .../maestro/.vscode/settings.json

Thank you.