Vscode: Iteration Plan for February 2020

Created on 10 Feb 2020  路  8Comments  路  Source: microsoft/vscode

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 https://github.com/microsoft/vscode/issues/91278.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

| Mark | Description |
| ------------------- | ------------------------------------------------- |
| :runner: | work in progress |
| :hand: | blocked task |
| :muscle: | stretch goal for this iteration |
| :red_circle: | missing issue reference |
| :large_blue_circle: | more investigation required to remove uncertainty |
| :black_circle: | under discussion within the team |

UX

Accessibility

Workbench

Editor

Languages

LSP / LSIF

  • [ ] :runner: Investigate into support for optimized LSP transport of JSON payloads (gzip, MessagePack) issue @dbaeumer
  • [x] LSP protocol enhancements (symbol tags, links in diagnostic messages) @dbaeumer
  • [x] [LSIF Web Page polish](https://github.com/microsoft/language-server-protocol/issues/928) @dbaeumer

HTML/CSS

TypeScript/JavaScript

Debug

DAP

SCM

Terminal

Tasks

API

Web

Extension Contributions

Engineering

Documentation

Deferred Items

iteration-plan
Source
picture egamma
👍14 ❤9 😄1

Most helpful comment

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.

picture jhpratt on 17 Feb 2020
👍5

All 8 comments

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

jvesouza picture jvesouza on 11 Feb 2020
👍4

@jvesouza Thank you very much for the pointers, let's continue the discussion here https://github.com/microsoft/vscode/issues/90446

isidorn picture isidorn on 11 Feb 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

Kroc picture Kroc on 14 Feb 2020
👍3

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.

jhpratt picture jhpratt on 17 Feb 2020
👍5

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.

gazzar picture gazzar on 19 Feb 2020
👎2 👍1

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?

Tyriar picture Tyriar on 19 Feb 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.

gazzar picture gazzar on 19 Feb 2020
👍1 

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

I think you can see, among others, this one: https://github.com/microsoft/vscode/issues/55440

kanlukasz picture kanlukasz on 22 Feb 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

trstringer picture trstringer  路  3Comments
borekb picture borekb  路  3Comments
sijad picture sijad  路  3Comments
sirius1024 picture sirius1024  路  3Comments
DovydasNavickas picture DovydasNavickas  路  3Comments