feat(store): debounce selectSignal by default

[arturovt]

In this commit, we make selectSignal debouncable by default. This means that changes originating from the state stream will not immediately update the signal but will instead occur as soon as possible (in the next microtask tick). By decoupling state signal updates from synchronous changes, we adhere to constraints on updates within effects. There are situations where actions dispatched within effects are synchronous, causing the state signal to also receive synchronous updates. This scenario can lead to an error indicating that signal writes are not permitted within effects.

Resolves #2180

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 18f8ede. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx run-many --target=test --all --configuration=ci --maxWorkers=4
• nx run-many --target=lint --all
• nx lint-types store
• nx run-many --target=build --all

---

Sent with 💌 from NxCloud.

[bundlemon]

BundleMon (Integration Projects)

Files updated (2)

Status	Path	Size	Limits
✅	Main bundles(Gzip) hello-world-ng17/dist-integration/main.(hash) .js	69.64KB (+187B +0.26%)	+1%
✅	Main bundles(Gzip) hello-world-ng16/dist-integration/main.(hash) .js	68.61KB (+143B +0.2%)	+1%

Total files change +330B +0.23%

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[markwhitfeld]

Oh nice, so this is able to determine the correct injection context at run time🎉.

[codeclimate]

Code Climate has analyzed commit 18f8ede and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 92.3% (50% is the threshold).

This pull request will bring the total coverage in the repository to 95.4% (0.0% change).

View more on Code Climate.

[simfyz]

@arturovt @markwhitfeld This is causing issues when using accessing signals inside dispatch. the signal value becomes null. Mostly when the default is null and values are set by an API call.

panda = select(ZooState.panda);

ngOnInit() {
    this.store.dispatch(new GetAnimals).pipe(takeUntilDestroyed(this.destroyRef)).subscribe(() => {
        const cutePanda = panda(); // value() is undefined here
    });
}