-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
November/December Iteration Plan #15099
Comments
I think everybody can agree<< removed gif>> killed fun This is a pretty exciting agenda.Can wait to see how it unfolds! @rebornix @alexandrudima If you're revisiting the diff viewer, could you look into a cool merge-mode feature like JetBrains has? Here's a video The one thing I am sad to see missing is custom inline widgety-things ala #3220. I understand your initial investigation into the concept wasn't promising, but don't give up!! OP mentions:
and a few other vague references to "contributable explorers.. but might it be wiser to address UI extensibility as a whole rather than a case by case basis? _This extensibility is the one thing that I believe Anyway, that's my 2¢. |
Sounds great! Since the diff viewer is going to be looked at -- a feature I would love to have (and others on my team have echoed) would be small buttons (or something) to be able to quickly move change blocks from on side to the other. Of course these would only be available if one side of the diff was editable. |
I agree with PHP support! A very promising extension is https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-intellisense You could help me with his work! |
Closing - November has been shipped |
This plan captures what we work on during November and early December. This iteration will be 6 weeks long. This is unusually long for us. We are an internationally distributed team and everybody in the team wants to enjoy the forthcoming holiday season while we still continue working as a closely knit team. Thus, it's 6 weeks this time. We will ship mid December.
Not unusual and still noteworthy: We will do several explorations that might or might not result in concrete deliverables in this or later releases.
Endgame Schedule
Monday - 5th December
Tuesday - 6th December
Wednesday - 7th December
About 80 issues were verified on 12/7
Thursday - 8th December
candidate
)OSSREADME.json
for built-in extensions based on differences to generatednpm-shrinkwrap.json
files if needed @ramya-rao-aFriday - 9th December
insider
builds @zurichMajor_Minor.md
in this repo directoryFriday- 9th December
Monday - 12th December
Insider
with hand-picked and reviewed candidate fixes @ramya-rao-aTuesday - 13th December
Wednesday - 14th December
HEAD
ofrelease/<x.y>
in formatx.y.z
@ramya-rao-ainsider
builds @kieferrmPlan Items
Our team uses a GitHub Project to track its work. GitHub does not support public Projects right now. Below is a summary of the top level plan items.
Legend for annotations:
Themes
Feedback
Issues to address community feedback:
API Improvements for Extensions
d.ts
file LSP#25 @dbaeumervscode.d.ts
Use non-nullable types in vscode.d.ts #6907 @jriekenreadonly
modifier invscode.d.ts
use new readonly modifier #12732 @jriekenLanguage support
jsconfig.json
for projects without commonjs modules TS#11554 @dbaeumerjsconfig.json
light bulb Remove jsconfig.json light bulb #15205 @mjbvzDebt Items
Issues to reduce our engineering debt:
vscode-textmate
compute simplified tokens. This will improve rendering performance as well as fix issues we see with several textmate themes. Compute theme & embedded modes information in vscode-textmate #15379 @alexandrudimavscode-textmate
changes Review themes in response tovscode-textmate
changes #15376 @aeschliExtension Contributions
Support/contribute to extensions:
Engineering
This section lists several engineering/development items that the team identified:
Feedback Channels
Explorations
We are continuously exploring options and ideas. Some might make it into future releases.
The text was updated successfully, but these errors were encountered: