The signalStore function could return two functions, one for provide and one for inject. about platform

[markostanimirovic]

For an example of what I mean, you can check the createInjectionToken function in the ngextension library.
https://ngxtension.netlify.app/utilities/injectors/create-injection-token/

The idea with [provide, inject] tuple is from initial SignalStore proposal.

The injection token's limitation is that it cannot be provided via the providers array without useFactory. That's the reason why the provide.. function is necessary for tokens. On the other hand, this is not needed for services (classes).

By the way, I opened an issue for this some time ago: angular/angular#49807

It would be convenient if the signalStore function, instead of returning the class to use for providing and injecting, returned two functions that act as injection function and provider function using the new standalone syntax.

Can you provide more details on why the [provide, inject] tuple instead of a single service seems more convenient to you?

As I mentioned, we started with this approach but changed it for two main reasons:

• Simplicity: There is no need for a different signature when SignalStore is provided at the root level. With [provide, inject] approach, the provide function is not needed for root-level stores.
• Testing: Service can be easily mocked