Open iamkinetic opened 1 month ago
have the same problem
@mishahrokhola Did you find any workaround?
@iamkinetic no. The only 1 thing is not to mock the component
@satanTime Do you think it's something we could try to fix (and create a PR if we find a fix)?
Do you have any pointer at where in the code we would have to look?
I ran into the same problem and to be honest I'm not sure if this library already officially supports signal inputs. The documentation doesn't mention anything about it, additionally you won't find any references to signal inputs in the library code.
Description of the bug
MockComponent on component imported from an external library does not work with InputSignal.
An example of the bug
This is the simplified imported component definition:
Used like this:
The
isInProgress
is using the@Input()
decorator and is correctly working/rendering. The isDisabled is a signal input and doesn't seem to be correctly rendered/working.If I remove the [IsDisabled]="true" from the html, the page renders correctly and the unit test are ok.
If I copy the component from the library directly in my angular project, the InputSignal is correctly working with MockComponent. Is something missing from the external library or is MockComponent not able to read the InputSignal from an exported component?
My unit test are using karma/jasmine (still using TestBed). The project itself is correctly running and the binding on the InputSignal is working outside of the unit tests.
The components library and my project are both using Angular 18 and i'm using ngMocks latest version.