Initial value not displayed when container has OnPush change detection strategy
See original GitHub issueWhen container has OnPush detection strategy, initial value not displayed at ng-select control.
After click or next change detection value will be displayed.
Found at alpha-12
Actual for beta.3
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:19
Top Results From Across the Web
Angular OnPush Change Detection - Avoid Common Pitfalls
Scenario 1 - Our Starting Point (default change detection). Let's have a look at a simple component that does not use yet OnPush...
Read more >onPush Detection strategy not working in angular 8
Above is the scenario where i am changing widget.widgetName in app-widget-settings component, where app-widget-settings consist of text box ...
Read more >Bug: Select doesn't have initial value when change detection ...
when change detection set to onPush, Select shows empty value. What are the steps to reproduce? Providing a Plunker (or similar) is the...
Read more >Understanding how Angular ChangeDetectionStrategy ...
In this article, we will observe and analyze how change detection works by going through a couple of cases where each case has...
Read more >Avoid common pitfalls when using OnPush change detection ...
When the OnPush change detection is declared as we see above, the change detection doesn't run automatically anymore. Instead, it listens for ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@meiuqer Sure, I’ll take a look.
Thanks for the response. Could you do one test for me? Of maybe you already did it. Can you test this with ‘ng build --aot’? Because i do exactly the same and it works with ‘ng serve’ and not with ‘ng build --aot’ and i cant, for the life of me, figure out why this can happen.
EDIT: nvm, forgot to add it to the metadat.json. I’m working in the compiled code.