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

Allow users to access persistent data from Zowe Explorer local storage #3180

Open
benjamin-t-santos opened this issue Oct 3, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@benjamin-t-santos
Copy link
Contributor

benjamin-t-santos commented Oct 3, 2024

Is your feature request related to a problem? Please describe.

In v2, persistent data like filter history and favorites for data sets, USS, and jobs were stored in the Visual Studio Code settings. This made it simple for extenders to access and read this data.
In v3, this data was moved to VS Code storage, and now there is no way for extenders to access it.

Describe the solution you'd like

I would like this persistent data to be accessible for extenders like it was in v2. This could be in the form of registered commands for getting/setting persistent data. You could also expose each resource's ZoweTreeProvider to extenders.

Describe alternatives you've considered

I tried accessing the ZE's new storage using the keys available in the Zowe Explorer API, but because I cannot access Zowe Explorer's extension context, there is no way for me to access its memento storage.

Additional context

@benjamin-t-santos benjamin-t-santos added the enhancement New feature or request label Oct 3, 2024
Copy link

github-actions bot commented Oct 3, 2024

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: New Issues
Development

No branches or pull requests

1 participant