Provide example of signal events being used outside of a store

[undsoft]

Information

Events source code contains an example of how Events can be used outside of a store:

platform/modules/signals/events/src/events-service.ts

Lines 62 to 72 in 7819972

	* \@Component({ /* ... *\/ })
	* class Counter {
	* readonly #events = inject(Events);
	*
	* constructor() {
	* this.#events
	* .on(increment)
	* .pipe(takeUntilDestroyed())
	* .subscribe(() => /* handle increment event *\/);
	* }
	* }

It may be a good idea to include it in documentation as well, because it is not immediately obvious you can do this.

Documentation page

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[rainerhahnekamp]

I don't think that this is something, that should be shown in the documentation. Doesn't seem to be a "mainstream pattern".

What is your use case? Why are you not able to handle that event in a SignalStore?

[PhilippMDoerner]

Where would e.g. an effect go that domain-wise does not obviously belong to single signal store but is something equally relevant for multiple signal stores?

Note: I do not use the signalstores event feature yet as at work we use the default store with full Redux pattern which is a pattern I heavily appreciate, so I often struggle when I give the docs a cursory read on how I'd want to squeeze a "normal" Redux pattern into it in a manner that will not struggle heavily..

[undsoft]

@rainerhahnekamp
Well, fair enough, I guess it's not a mainstream pattern.
I am working on a game and I have a gamePaused event that I was going to listen to in some components. It's true that I can listen to a selector instead.

It's just that as I was selecting the architecture for my application, it would have been good to know what's possible beforehand.

[markostanimirovic]

The example is already part of the API (JS) docs.

The "Events" documentation page contains the main use cases. Events is an Angular service and can be injected regularly as any other service where needed.