Skip to content

Service in component shared folder - export in index.ts is incorrect #1480

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
esinek opened this issue Jul 28, 2016 · 4 comments
Closed

Service in component shared folder - export in index.ts is incorrect #1480

esinek opened this issue Jul 28, 2016 · 4 comments

Comments

@esinek
Copy link

esinek commented Jul 28, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    Windows 7
  2. Versions. Please run ng --version. If there's nothing outputted, please run
    in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.10
node: 6.2.2
os: win32 x64
  1. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
ng g component myTest
ng g component my-test/mySettings
ng g service my-test/my-settings/shared/mySettings
  1. The log given by the failure. Normally this include a stack trace and some
    more information.
    no error returned from CLI
  2. Mention any other details that might be useful.
    The exports in the index.ts file at the service level (src/app/my-test/my-settings/shared/index.ts) exports the incorrect file. It should be:
    export * from './my-settings.service'
    but instead is:
    export * from './mySettings.service'

Thanks! We'll be in touch soon.

@esinek
Copy link
Author

esinek commented Jul 28, 2016

same issue when service in myTest component's shared folder:

ng g service my-test/shared/mySettings

@esinek esinek changed the title Service export in index.ts incorrect when 2 components deep Service in component shared folder - export in index.ts is incorrect Jul 28, 2016
@filipesilva
Copy link
Contributor

Definitely a bug, related to #1434

@Gelio
Copy link
Contributor

Gelio commented Sep 23, 2016

This should be closed, as mentioned by @filipesilva in #1434

@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants