@devversion as we discussed previously regarding the signal input failing in testcases #56998 (comment) . I created a separate PR for the issue, also attaching the screenshot of the error

Thank you @sheikalthaf. I will check this out soon! appreciate it

I've looked into it a bit. Thanks for the PR. that's great for debugging.

The issue is:

• The application code is compiled AOT — that's good!
• The test code is not compiled with AOT — that's generally okay, but NOT here with Bazel as the Angular JIT transforms don't run, so input() etc. are not detected and break.

Fixing the second point is easy, just use ng_module. But then, we still see failures. That is because the test uses TestBed.overrideComponent! Seems like this is not working well with signal inputs, or other non-decorator APIs.

That is because the setClassMetadata calls (generated for JIT) are used to re-compile the component with the overrides — but there is no decorator for the input() calls, hence this metadata is lost.

Options I could see:

• Smartly merging directly with the original component metadata in TestBed.
  • Will be hard to detect output as it's non-distinguishable from decorator outputs.
  • I guess, we could fully re-use inputs, queries etc. metadata instead of relying on prop decorators..?
• Adding synthetic prop decorators to setClassMetadata.
  • Would be great to re-use the JIT transforms.. but those need an import manager; so needs a bit of refactoring!

Let's close this in favor of a tracking issue. #57944. Thanks again!

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}