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.

Sign up for GitHub

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

Jump to bottom

VS Code workspace related changes. #453

Open

5 tasks

aparnamichael opened this issue Dec 19, 2024 · 1 comment

Assignees

Labels

Epic

Milestone

Contributor

aparnamichael commented Dec 19, 2024 •

edited by JoshwinThomasIBM

Loading

aparnamichael added the Epic label

aparnamichael added this to the Next milestone

aparnamichael assigned JoshwinThomasIBM

aparnamichael added this to Open Liberty Developer Experience

github-project-automation bot moved this to New Issues in Open Liberty Developer Experience

aparnamichael moved this from New Issues to In Progress in Open Liberty Developer Experience

JoshwinThomasIBM moved this from In Progress to Parked in Open Liberty Developer Experience

Contributor

JoshwinThomasIBM commented Jan 15, 2025

We need answers for the below to proceed with the workspace related changes in this epic . These are raised in vs code discussions forum.

How can we retrieve the workspace name after the save operation in the deactivate() method?

Can we hook into the workspace save workflow when the user tries to save the workspace?

Can VS Code determine if a session is active based on a provided session ID?

Is it possible to clear data stored in the global state directly from the deactivate() method of an extension?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment