-
-
Notifications
You must be signed in to change notification settings - Fork 208
fix(cdk): list-template-manager should always emit latest value #1460
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
base: main
Are you sure you want to change the base?
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit a8258e7. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 5 targetsSent with 💌 from NxCloud. |
Codecov Report
@@ Coverage Diff @@
## main #1460 +/- ##
==========================================
+ Coverage 74.95% 76.81% +1.86%
==========================================
Files 151 113 -38
Lines 2951 2295 -656
Branches 531 392 -139
==========================================
- Hits 2212 1763 -449
+ Misses 617 429 -188
+ Partials 122 103 -19
Flags with carried forward coverage won't be shown. Click here to find out more. |
I started to investigate to find out why coverage reports are broken. |
Bug
The list template manager emits an empty array after it received a value and detected no changes to render. This leads to unexpected value emissions through
rxFor
s rendercallback.Fix
The list template manager should always emit the latest set of data, even if no change was detected on new value input.
This is e.g. useful in scenarios where you rely on the renderCallback in order to hide a loading spinner after an asynchronous operation.
I'm thinking about a search bar triggering an http request and returning the same data as before.
rxFor
wouldn't render any new change, but the renderCallback should still indicate the change got processed.