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
The new Concerto.instanceOf call works on non-valid data so can easily be confusing and give the impression that an object is an instance of a class even when it isn't.
[This could be considered "as designed" but I think the call and doc are misleading and will lead to confusion and users believing they have performed validation when they haven't.]
Bug Report 🐛
The new
Concerto.instanceOf
call works on non-valid data so can easily be confusing and give the impression that an object is an instance of a class even when it isn't.[This could be considered "as designed" but I think the call and doc are misleading and will lead to confusion and users believing they have performed validation when they haven't.]
Example:
Run:
Expected Behavior
Instance of should fail for non valid data.
Current Behavior
Instance of sometimes returns true for non valid data.
Possible Solution
I think the current call is fundamentally not between an object and a class, but simply looking into the type hierarchy. I would either:
The text was updated successfully, but these errors were encountered: