Skip to content

fix: declare ROUTER_PROVIDERS on root component rather than bootstrap #301

Closed

Description

@cburgdorf

According to this style guide it's a best practice to declare the providers on the root component rather than the bootstrap.

Activity

  1. filipesilva commented on Mar 14, 2016

    @filipesilva
    Contributor

    We're actually waiting for a definite style guide to change all the blueprints to something a little better structured, which is why these providers are still in the bootstrap.

    That being said, I won't say no to a PR fixing this bit for now.

  2. cburgdorf commented on Mar 15, 2016

    @cburgdorf
    ContributorAuthor

    Ah ok. Feel free to close the PR if you rather like to wait on a definite style guide. I sent the PR as we are teaching people to not maintain providers in the bootstrap in our thoughtram training. We are soon switching over to use angular-cli in our workshops hence I thought I sent a PR for this change.

  3. filipesilva commented on Mar 16, 2016

    @filipesilva
    Contributor

    Really? That's great news for the CLI!

    I hope you come back to the cli repo with a lot of tasty feedback from your trainees :D

  4. angular-automatic-lock-bot commented on Sep 5, 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.

  5. locked and limited conversation to collaborators on Sep 5, 2019
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions