Skip to content

Support for Typescript 2.8 #23092

Closed
Closed

Description

@pulsejet

I'm submitting a...


[x] Feature request

Current behavior

Throws an error for TS 2.8+ which can optionally be overridden.

Expected behavior

2.7 is now supported (8449eb8), but since 2.8.1 is already here, would be nice to have support for it officially.

Activity

  1. changed the title [-]Add support for Typescript 2.8[/-] [+]Support for Typescript 2.8[/+] on Mar 30, 2018
  2. added this to the needsTriage milestone on Apr 2, 2018
  3. alexeagle commented on Apr 2, 2018

    @alexeagle
    Contributor

    I think we want to do this for rc.2, right @IgorMinar ?

  4. sandangel commented on Apr 2, 2018

    @sandangel

    Please do. I really really want conditional type.

  5. added
    area: packagingIssues related to Angular's creation of npm packages
    area: coreIssues related to the framework runtime
    featureLabel used to distinguish feature request from other issues
    on Apr 3, 2018
  6. modified the milestones: needsTriage, Backlog on Apr 3, 2018
  7. IgorMinar commented on Apr 3, 2018

    @IgorMinar
    Contributor

    @alexeagle I don't think so. it's a high risk change. This will have to wait until 6.1 due in May.

  8. modified the milestones: Backlog, on Apr 11, 2018
  9. darrenmothersele commented on Apr 24, 2018

    @darrenmothersele

    I'd love to be able to use unionize v2 with ngrx. Needs Typescript 2.8 support.

  10. pburgmer commented on May 8, 2018

    @pburgmer
    Contributor

    Would be great to see this in CLI 6.1

  11. self-assigned this
    on May 8, 2018
  12. IgorMinar commented on May 8, 2018

    @IgorMinar
    Contributor

    Closing in favor of #23779. Please follow that issue for updates.

  13. angular-automatic-lock-bot commented on Sep 13, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  14. locked and limited conversation to collaborators on Sep 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: build & ciRelated the build and CI infrastructure of the projectarea: coreIssues related to the framework runtimearea: packagingIssues related to Angular's creation of npm packagesfeatureLabel used to distinguish feature request from other issuesfreq4: critical

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions