Skip to content

Changing an Interface doesn't seem to live reload it in the dev server #6438

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
KyleBastien opened this issue May 24, 2017 · 4 comments
Closed
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity1: confusing

Comments

@KyleBastien
Copy link

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.0.4
node: 7.8.0
os: darwin x64
@angular/animations: 4.1.3
@angular/common: 4.1.3
@angular/compiler: 4.1.3
@angular/core: 4.1.3
@angular/forms: 4.1.3
@angular/http: 4.1.3
@angular/material: 2.0.0-beta.5
@angular/platform-browser: 4.1.3
@angular/platform-browser-dynamic: 4.1.3
@angular/router: 4.1.3
@angular/cli: 1.0.4
@angular/compiler-cli: 4.1.3

Repro steps.

Have a an app running in the dev server, and be referencing a simple interface and some properties from it somewhere in code, for example if you have an interface Person and then are referencing property id which is of type string. If you change the interface, and for example change the type of id to be number then you will start to get errors in the CLI's dev server about how the property is still of style string. It seems that the CLI's dev server doesn't automatically pick up on interface changes like this and instead you need to restart the server.

The log given by the failure.

N/A

Desired functionality.

That the CLI's dev server automatically updates when you make type changes to the interface and they are correct reflected on the next live reload.

@natedsaint
Copy link

+1

@Brocco Brocco added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity1: confusing labels May 25, 2017
@filipesilva
Copy link
Contributor

Dupe of #5634

@KyleBastien
Copy link
Author

Ahhh! Thanks @filipesilva for pointing out the dupe!

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity1: confusing
Projects
None yet
Development

No branches or pull requests

4 participants