Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error loading team config file when default base profile is nested and non-existent #3372

Open
t1m0thyj opened this issue Dec 23, 2024 · 1 comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.

Comments

@t1m0thyj
Copy link
Member

t1m0thyj commented Dec 23, 2024

Describe the bug

If a team config file defines a default base profile that is nested (e.g. base.lpar1) and does not exist, then ZE fails to load.

To Reproduce

Run zowe config set defaults.base "base.invalid" and reload VS Code.

Expected behavior

Zowe Explorer should load successfully since there is not a JSON syntax error.

Screenshots

image

Desktop (please complete the following information):

  • OS:
  • Zowe Explorer Version:
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?

Additional context

Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@zFernand0 zFernand0 added priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. labels Jan 2, 2025
@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe Explorer for VS Code Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants