Every time i have to re-compile the code if i refer to a new image from assets folder

I’m submitting a Issue regarding img tag

[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

I have some image paths from db which is coming on Angular side dynamically. Every time there is a new image, I have to re-compile the angular code other wise it gives 404 Resource Not Found error. This is really annoying.

Expected behavior

Ideally there must be no need to re-compile the code for every new image.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

If we have tag in our html file and it is getting image src dynamically, so for every new image we have to re-compile the code and then it will get the image, otherwise it will give 404 Resource Not Found error.

Environment

Angular version: 6.1.5


Browser:
- [x] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 8.11.4  
- Platform: Windows 

Others:

[ericmartinezr]

Hello, we reviewed this issue and determined that it doesn’t fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular.

If you are wondering why we don’t resolve support issues via the issue tracker, please check out this explanation.

---

Not related to angular. Barely likely to be angular-cli’s issue.

[angular-automatic-lock-bot[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.}