Jits

@cexbrayat – that sounds good! Let me know if I can help in any way.

Hi @rainerhahnekamp. I'd be happy to lend a hand — let me know if I can help in any way. (And, sorry, I realise I haven't responded to yours and...

@rainerhahnekamp — (I'm commenting here and not directly on #4461 as you requested, as I think my comment isn't directly related to your PR and shouldn't impact it). The testing...

Thanks @rainerhahnekamp. Especially for your invaluable work here. I should add: I haven't really delved too deeply into testing stores (and store dependencies) just yet, but will likely do so...

It looks like, at the moment, Angular themselves test out signal inputs by manually defining and using wrapper components (i.e. without any reflection on the available inputs and types): https://github.com/angular/angular/blob/e2272750878e1f74e59121e76a01e910ad1ac607/integration/cli-signal-inputs/src/app/greet.component.spec.ts#L20-L27

Potentially useful: the Spectator library is being updated to support signal inputs: https://github.com/ngneat/spectator/pull/638

How about when using Jasmine? (The default out-of-the-box experience that Angular provides)

@cuddlecake — it's useful to know, thanks for sharing. Aside: Angular does have official [experimental support for Jest](https://blog.angular.io/moving-angular-cli-to-jest-and-web-test-runner-ef85ef69ceca); I wonder where that will go.

Nuxt Content has [a very nice way](https://content.nuxt.com/usage/content-directory#ordering) of supporting custom ordering, by allowing numeric prefixes in the filename, which it then ignores when generating the slug/ID.

Is there anything that could be done to get v6.0.6 released? This is blocking Angular v18 upgrades. For now, I'm using the [6.0.6-canary.5cfad21](https://www.npmjs.com/package/rxfire/v/6.0.6-canary.5cfad21) version, which doesn't seem ideal.