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

Update VS Code requirement to 1.65 #1134

Merged
merged 1 commit into from
Mar 28, 2022
Merged

Update VS Code requirement to 1.65 #1134

merged 1 commit into from
Mar 28, 2022

Conversation

CsCherrYY
Copy link
Contributor

since we will support lazy loading in microsoft/java-debug#401, the requirement of this feature is introduced in VS Code 1.65, see: https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_65.md#lazy-variables

@testforstephen
Copy link
Contributor

Since the lazy variable implementation is compatible with old vscode client, it's not necessary to force updating VS Code version. WDYT?

@CsCherrYY
Copy link
Contributor Author

Since the lazy variable implementation is compatible with old vscode client, it's not necessary to force updating VS Code version. WDYT?

Agree that it's not necessary, but if you run this version in an old client, you will see a similar behavior like microsoft/vscode#134450 (comment), for the getter of address. it will introduce an extra node so I'm not sure if it's a good UX. It's up to you.

@testforstephen
Copy link
Contributor

@CsCherrYY Could you pls resolve the conflicts?

@testforstephen testforstephen merged commit 6d32418 into main Mar 28, 2022
@testforstephen testforstephen deleted the cs-lazy-loading branch March 28, 2022 04:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants