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

TypeScript 3.7 Iteration Plan #33352

Open
DanielRosenwasser opened this issue Sep 10, 2019 · 5 comments

Comments

@DanielRosenwasser
Copy link
Member

commented Sep 10, 2019

This document outlines our focused tasks for TypeScript 3.7, as well as some of the discussion that explains how/why we prioritized certain work items. Nothing is set in stone, but we will strive to complete them in a reasonable timeframe.

Dates

Date Event
August 28th TypeScript 3.6 Release
September 27th Create 3.7 Beta (3.7.0) Build for Testing
October 1st TypeScript 3.7 Beta Release
October 18th Create 3.7 RC (3.7.1) Build for Testing
October 22nd TypeScript 3.7 RC Release
November 1st Create 3.7 Final (3.7.2) Build for Testing
November 5th TypeScript 3.7 Final Release 🚀

Work Items

Expected Work Items

Deferred Work Items

None from planning meeting


Planning Meeting Notes

Motivations

  • Bug backlog

  • Goals and current 6-month roadmap

  • GitHub user feedback (👍s)

  • Feedback from customer interviews, social media, past iteration plans

  • Visual Studio and Visual Studio Code feedback, as well as new functionality demands

  • Actionable PRs (need to make a call)

  • Language

    • Type System Innovation
      • Assertion Signatures
      • Recursive Type References
    • Standards Conformance
      • ECMAScript Private Fields
      • Nullish Coalescing
      • Optional Chaining
      • Top level await
      • Transition plan for class fields
  • Compiler

  • Infrastructure

    • Migrate repo to ESLint
    • Investigate smaller package publish
      • Might have ideas for removing unnecessary files.
    • Dual-publishing @types on GitHub package registry
      • Today, types packages are automatically fetched to power IntelliSense in VS and VS Code.
      • GitHub now provides its own registry.
      • We want to ensure that there is some level of redundancy.
  • Editor Productivity

    • Call hierarchy
    • Polishing auto-import functionality (fixing issues, adding functionality)
      • Just expect more to come in.
    • Project references improvements
      • Opening unbuilt project reference solutions (git clone scenarios)
      • Delayed loading of projects (improving performance and memory consumption)
  • Website and Documentation

    • New Handbook
      • Finishing up chapters (Enums and Modules) in core handbook
    • Redesign
      • Core messaging
      • Samples
      • New community page for meetups/conferences
      • Integrating the new handbook into the site
      • Ensure full accessibility
  • Stability

    • TSServer crawler
      • Currently takes a fixed set of repos
        • That's fine.
  • Performance

    • Rolling Issues
    • Experiments in Perf
      • Can we incrementally bind, reuse checking results, etc.?
    • Customer Development/Investigation
      • Establish hypotheses
      • Validate/invalidate
      • Concept/value testing
      • Implementation
    • Get performance data from TSServer crawler work.
@AnyhowStep

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

Nullish Coalescing

Links to "Top Level Await" issue

@ahejlsberg

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

@DanielRosenwasser Fixed link to Nullish Coalescing and added Recursive Type References.

@DanielRosenwasser

This comment has been minimized.

Copy link
Member Author

commented Sep 10, 2019

Thanks @AnyhowStep and @ahejlsberg. Additionally, I've made a change to the schedule. We will be reducing the feature period given that there's a convenient opportunity to align with Visual Studio, and we feel like the planned features are all individually in a good place.

@j-oliveras

This comment has been minimized.

Copy link
Contributor

commented Sep 15, 2019

Someone should move --declaration and --isolatedModules on roadmap to version 3.7 (currently on 3.6).

@vvakame

This comment has been minimized.

Copy link
Contributor

commented Oct 3, 2019

Does Auto-inserted await for completions and Call Hierarchy support on roadmap move to v3.7? It's not included in v3.6.3. right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.