Skip to content

route-config.ts is not created #439

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

Closed
vapits opened this issue Apr 15, 2016 · 6 comments
Closed

route-config.ts is not created #439

vapits opened this issue Apr 15, 2016 · 6 comments

Comments

@vapits
Copy link

vapits commented Apr 15, 2016

  1. OS. El Capital (but also on Win 10)
  2. Versions.
    angular-cli: 0.0.31
    node: 5.10.1

Hi there,
amazing tool!

I'm (and my team) having the following issue.
When we are generating a new _route_ then the _route-config_ file is never created. Even with thin the other created files (component etc) the Routeconfig stays empty.

I didn't manage to find something that explains that here on as I tried to make it work.

Any ideas? Is this a known behaviour or bug? The docs doesn't provide such info.

@vapits vapits changed the title route-config.js is not created route-config.ts is not created Apr 15, 2016
@hansl
Copy link
Contributor

hansl commented Apr 15, 2016

The CliRouterConfig has been deprecated in favor of updating the parent route source file instead.

Are you on 0.0.31? You can safely delete that file now and remove its import and usage in your routes.

@hansl hansl closed this as completed Apr 15, 2016
@vapits
Copy link
Author

vapits commented Apr 18, 2016

@hansl Yes I'm on the 0.0.31.
So based to the docs, when I'm generating a new route what should I expect?
Just the files so I have to go and create the route config for each route? Then what is the purpose of generating new route?

@Brocco
Copy link
Contributor

Brocco commented Apr 18, 2016

@vapits the generation of routes has been and currently is a pain point. This has been addressed in PR #427 and will continue to be refined. You can take advantage of this by working off of a local version of this repo, or await the next release of the CLI to npm.

@vapits
Copy link
Author

vapits commented Apr 19, 2016

Thx @Brocco for your answer.

PR is closed though, still have thoughts on the implementation? Can I help somehow?

@Brocco
Copy link
Contributor

Brocco commented Apr 19, 2016

@vapits the PR is closed because it was merged in. I do appreciate the offer for help though 🎉👍

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants