You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After finishing these steps i get warning: DEPRECATION: The matcher factory for "ɵ0" accepts custom equality testers, but this parameter will no longer be passed in a future release. See <https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0#matchers-cet> for details.
It looks like when ngcc compiles spectator, it adds custom matchers and functions to customMatchers array:
As you can see ngcc added ɵ0, the reference to hasProperty function
So, it looks like functions are added to the array that should not be there (hasProperty, for example). When these functions added to customMatchers, jasmine tries to use them as custom matchers and fails.
Some tests written with spectator start failing after upgrading jasmine-core to 3.99.1
Any thoughts?
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
DEPRECATION: The matcher factory for "ɵ0" accepts custom equality testers, but this parameter will no longer be passed in a future release. See <https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0#matchers-cet> for details.
Please provide the environment you discovered this bug in
Is this a regression?
No
Description
After finishing these steps i get warning:
DEPRECATION: The matcher factory for "ɵ0" accepts custom equality testers, but this parameter will no longer be passed in a future release. See <https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0#matchers-cet> for details.
It looks like when ngcc compiles spectator, it adds custom matchers and functions to customMatchers array:
As you can see ngcc added ɵ0, the reference to hasProperty function
So, it looks like functions are added to the array that should not be there (hasProperty, for example). When these functions added to customMatchers, jasmine tries to use them as custom matchers and fails.
Some tests written with spectator start failing after upgrading jasmine-core to 3.99.1
Any thoughts?
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in
Anything else?
No response
Do you want to create a pull request?
No
The text was updated successfully, but these errors were encountered: