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

Iteration Plan for January 2024 #201255

Closed
39 of 67 tasks
kieferrm opened this issue Dec 20, 2023 · 2 comments
Closed
39 of 67 tasks

Iteration Plan for January 2024 #201255

kieferrm opened this issue Dec 20, 2023 · 2 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan

Comments

@kieferrm
Copy link
Member

kieferrm commented Dec 20, 2023

This plan captures our work in January. This is a 4-week iteration. We will ship in early February.

Endgame

  • January 23, 2024: Endgame begins
  • January 26, 2024: Endgame done

The endgame details for this iteration are tracked here.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark Description
🏃 work in progress
blocked task
💪 stretch goal for this iteration
🔴 missing issue reference
🔵 more investigation required to remove uncertainty
under discussion within the team
a large work item, larger than one iteration

Accessibility

Workbench

Code Editor

Search

Notebook Editor

Jupyter Notebooks

WebAssembly Support

  • Research options for shared memory and object management between WASI threads that are mapped to workers vscode-wasm#153 @dbaeumer

Languages

Python

Language Server Protocol

TypeScript

Source Control

Testing

Debug

Debug Adapter Protocol

API

Extensions

Extension Contributions

Engineering

Electron


Deferred

@kieferrm kieferrm added the iteration-plan-draft VS Code - Upcoming iteration plan (Draft) label Dec 20, 2023
@kieferrm kieferrm added this to the December / January 2024 milestone Dec 20, 2023
@kieferrm kieferrm changed the title Iteration Plan for January 2024 [DRAFT] Iteration Plan for January 2024 Jan 3, 2024
@kieferrm kieferrm added iteration-plan VS Code - Upcoming iteration plan and removed iteration-plan-draft VS Code - Upcoming iteration plan (Draft) labels Jan 3, 2024
@kieferrm kieferrm pinned this issue Jan 3, 2024
@Cpt-Falcon
Copy link

Cpt-Falcon commented Jan 16, 2024

Any word on whether copy paste is going to be fixed? You can't copy a variable during debugging without visual studio truncating saying "...". Quite a nuisance. Only way to get the contents of a larger variable is to write it out to a json file. Visual studio 2022 doesn't have this problem and limitation. I would understand if it truncated past 1000, but truncating it at like 20 is ridiculous. Maybe put a setting in the vs code settings that does not restrict on copying large variable values from the debugger

@jstm88
Copy link

jstm88 commented Feb 1, 2024

How about addressing the fact that extensions are constantly able to spam the "Output" panel and there is no way to prevent it?

I opened #203478 in an attempt to get the discussion in #105270 restarted, but all mentions of this problem keep getting incorrectly closed as "duplicates" because the original report from over 6 years ago was closed without fully understanding the issue.

Not sure what users are supposed to do when a rogue mod starts closing valid issues and then not even looking at the discussion where users are calling for it to be reopened...

@kieferrm kieferrm closed this as completed Feb 2, 2024
@kieferrm kieferrm unpinned this issue Feb 2, 2024
@microsoft microsoft locked and limited conversation to collaborators Jun 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
iteration-plan VS Code - Upcoming iteration plan
Projects
None yet
Development

No branches or pull requests

10 participants
@joaomoreno @kieferrm @alexdima @sbatten @Cpt-Falcon @aiday-mar @jstm88 and others