Skip to content

fix(@angular/cli): fix import path for component when importing into … #7284

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

Merged
merged 1 commit into from
Aug 23, 2017

Conversation

andrewkww
Copy link
Contributor

…a module

This is similar to 86021a0.

Fix #7135

@hansl
Copy link
Contributor

hansl commented Aug 8, 2017

Hi @andrewkww,

Could you add a test so we prevent readding issue #7135 in the future? Thanks!

@andrewkww
Copy link
Contributor Author

@hansl Yup, added tests for other blueprints too.

@exequiel09
Copy link

Been waiting for this. I hope this PR will be merged soon. Thanks for the awesome work.

@hansl
Copy link
Contributor

hansl commented Aug 9, 2017

We're in the process of moving all our blueprints to Schematics. @Brocco is doing that work in #7090. Let's see if the issue happens still after that PR (some pathing problems were fixed because of the nature of Schematics which is stricter WRT paths).

I'm keeping this PR open but know that it will be obsolete. If the issue still happens, I'll check in with you that you make the change in the proper place on the Schematics repo.

Thakns!

@andrewkww andrewkww force-pushed the fix-module-path-component branch from a0ab547 to cffa68d Compare August 10, 2017 02:02
@cyrilletuzi
Copy link
Contributor

@hansl Why not include this PR in 1.3 ? I suppose schematics will have to wait for 1.4, meaning we will stay a more few weeks with this regression (and very annoying) issue.

@andrewkww
Copy link
Contributor Author

andrewkww commented Aug 12, 2017

@hansl Given the number of people running into the issue, it seems like a good idea to at least merge the change into 1.3.x.

@andrewkww andrewkww force-pushed the fix-module-path-component branch from 56b225f to 87a8c89 Compare August 17, 2017 23:20
@andrewkww
Copy link
Contributor Author

Looks like the issue is now fixed in master. It'd still be good to include the tests that I have, since they test for the issue.

Also, the issue still exists in 1.3.x and 1.4.x. I think it's still a good idea to have the fix applied there. Let me know if you want the fix in those branches, and I can submit a pull request to those branches.

@hansl
Copy link
Contributor

hansl commented Aug 18, 2017

@andrewkww Master is not what's being released in 1.3.0, so this PR might actually skip master and be merged in 1.3.x directly.

@andrewkww andrewkww force-pushed the fix-module-path-component branch from 87a8c89 to 3814683 Compare August 18, 2017 01:58
@andrewkww
Copy link
Contributor Author

Yes, but since this PR is set to merge into master, I've removed the patch so that the commits only contains the tests. This should be good to merge into master. If you want the fix for blueprint that I had previously, I can create a separate pull requests, one for 1.3.x and one for 1.4.x.

@hansl
Copy link
Contributor

hansl commented Aug 23, 2017

Please create one for 1.3.x. We will only have the tests for 1.4.x.

@hansl hansl merged commit cff3270 into angular:master Aug 23, 2017
@hansl
Copy link
Contributor

hansl commented Aug 23, 2017

@andrewkww I went ahead and did a PR for your 1.3.x branch and merged it. It's going to be out today. Thanks!

andrewkww added a commit to andrewkww/angular-cli that referenced this pull request Aug 24, 2017
@andrewkww andrewkww deleted the fix-module-path-component branch August 24, 2017 02:03
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this pull request Apr 23, 2018
@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 12, 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

Successfully merging this pull request may close these issues.

Angular cli Generates Wrong Directory Path in app.module.ts
5 participants