-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use equality instead of identity to compare types #533
Conversation
In some cases, possibly when MsgGenerator is defined or imported from different modules, the types can be equivalent but are not the same instance. In these cases, the identity check would fail and some plans would be excluded where they shouldn't be. Using equality checks instead mean it shouldn't matter where the MsgGenerator type was defined as all instances should be equal.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #533 +/- ##
=======================================
Coverage 91.10% 91.10%
=======================================
Files 40 40
Lines 1787 1787
=======================================
Hits 1628 1628
Misses 159 159 ☔ View full report in Codecov by Sentry. |
copied from the Jira ticket
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking at this!
This issue is now extending to equality when deployed on i22.
|
In some cases, possibly when MsgGenerator is defined or imported from
different modules, the types can be equivalent but are not the same
instance. In these cases, the identity check would fail and some plans
would be excluded where they shouldn't be. Using equality checks instead
mean it shouldn't matter where the MsgGenerator type was defined as all
instances should be equal.