Implement better technique to detect signal within @cypress/angular-signals test harness

[AtofStryker]

What would you like?

I would like to have a better way to detect Angular signals within the @cypress/angular-signals test harness.

Why is this needed?

Currently, within the @cypress/angular-signals test harness, we determine what type of signal() an angular signal is based on the Symbol(SIGNAL) property and some other expected keys on the object. This isn't instance based or constructor based, since we can't determine the instanceof of a function. However, avoiding to check for arbitrary keys and values and deterministically figuring out what signal() is passed in without interference would be ideal.

Other

No response

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[cypress-app-bot]

This issue has been closed due to inactivity.