Skip to content

Tree-Shakeable Providers Followup Work #22830

Closed

Description

@alxhub

Near term

  • Determine whether the Injector -> INJECTOR rewrite should happen in render2 mode (requires NgModuleRef and ComponentRef injectors to handle it)
  • Allow injection of root-scope tokens without a current injector, via inject().
  • Convert InjectableCompiler to the render3 function style compiler (compileInjectable).
  • Inheritance between injectables.
  • Unify inject with directiveInject

Longer term

  • Disallow render2-style providers in R3Injector by default. Have a Render2ProviderFeature which converts render2-style providers to render3-style providers.
  • Investigate supporting multi-providers in the same way.
  • convert as many Angular services as possible to be tree-shakeable.

Activity

  1. added this to the needsTriage milestone on Mar 16, 2018
  2. added
    featureLabel used to distinguish feature request from other issues
    on Mar 20, 2018
  3. modified the milestones: needsTriage, Backlog on Mar 20, 2018
  4. angular-robot commented on Jun 4, 2021

    @angular-robot
    Contributor

    Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

    Find more details about Angular's feature request process in our documentation.

  5. angular-robot commented on Jun 24, 2021

    @angular-robot
    Contributor

    Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

    We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

    You can find more details about the feature request process in our documentation.

  6. alxhub commented on Jul 9, 2021

    @alxhub
    MemberAuthor

    Closing as obsolete.

  7. angular-automatic-lock-bot commented on Aug 9, 2021

    @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.

  8. locked and limited conversation to collaborators on Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: compilerIssues related to `ngc`, Angular's template compilerfeatureLabel used to distinguish feature request from other issues

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions