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 February 2020 #90371

Closed
42 of 54 tasks
egamma opened this issue Feb 10, 2020 · 8 comments
Closed
42 of 54 tasks

Iteration Plan for February 2020 #90371

egamma opened this issue Feb 10, 2020 · 8 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan
Milestone

Comments

@egamma
Copy link
Member

egamma commented Feb 10, 2020

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

Endgame

  • February 24th, 2020: Endgame begins
  • February 28th, 2020: Endgame done

The endgame details for this iteration are tracked in #91278.

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

UX

Accessibility

Workbench

Editor

Languages

LSP / LSIF

HTML/CSS

TypeScript/JavaScript

Debug

DAP

SCM

Terminal

Tasks

API

Web

Extension Contributions

Engineering

Documentation


Deferred Items

@egamma egamma added the iteration-plan-draft VS Code - Upcoming iteration plan (Draft) label Feb 10, 2020
@egamma egamma added this to the February 2020 milestone Feb 10, 2020
@egamma egamma changed the title Iteration Plan for January 2020 Iteration Plan for February 2020 Feb 10, 2020
@egamma egamma pinned this issue Feb 10, 2020
@kieferrm kieferrm added iteration-plan VS Code - Upcoming iteration plan and removed iteration-plan-draft VS Code - Upcoming iteration plan (Draft) labels Feb 10, 2020
@jvesouza
Copy link

First of all forgive me if the comments are not relevant or if they are not in the right place.
I was excited by the fact that accessibility in linux is being taken into account by the VSCode accessibility team. I have been using orca for over 10 years and I believe that VSCode will greatly increase my productivity in this environment.

Here are some links that may help with research:

https://wiki.gnome.org/Projects/Orca/Chromium
https://wiki.gnome.org/Projects/Orca
https://mail.gnome.org/mailman/listinfo/orca-list

@isidorn
Copy link
Contributor

isidorn commented Feb 11, 2020

@jvesouza Thank you very much for the pointers, let's continue the discussion here #90446

@Kroc
Copy link

Kroc commented Feb 14, 2020

Can I ask please that this issue be looked at this month? #87347 "New minimum width of panel is too wide on 1366px screen", this is making it awkward for laptop users

@jhpratt
Copy link

jhpratt commented Feb 16, 2020

Can we please get someone to look into #23991? It's an issue that has been around for years and affects a number of people. It doesn't necessarily have to be fixed immediately; even having eyes on it would be an improvement.

@gazzar
Copy link

gazzar commented Feb 19, 2020

There's an editor item to "Improve the discoverability of the column selection support." This seems like a pointless waste of effort. Apart from column selection being already supported and documented, I actually don't see a lot of benefit to the current implementation of column selection in VSCode. Usually the point of column selection is to be able to move blocks of code, i.e. cut or copy the selection then paste it elsewhere in the code, but pasting columns basically doesn't work in VSCode. Until that is fixed, there is little benefit to improving discoverability of a feature that is only useful if you happen to want to delete columns of code and not also paste them back somewhere.

@Tyriar
Copy link
Member

Tyriar commented Feb 19, 2020

but pasting columns basically doesn't work in VSCode

@gazzar do you know if there is an issue tracking the problems with column selection copy+pasting?

@gazzar
Copy link

gazzar commented Feb 19, 2020

but pasting columns basically doesn't work in VSCode

@gazzar do you know if there is an issue tracking the problems with column selection copy+pasting?

Hi @Tyriar, the main one is #5940. There is also #43145 which is to do with pasting blocks at the ends of lines. I don't really think it is different, but was closed and reopened, perhaps because it contains extra detail about the behaviour of how this works in other editors such as Visual Studio.

@kanlukasz
Copy link

* [ ]  🏃 Explore global undo/redo of workspace edits @alexdima

I think you can see, among others, this one: #55440

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