-
Notifications
You must be signed in to change notification settings - Fork 17
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
Fix streamer lookup #227
Fix streamer lookup #227
Conversation
Here is the actual MWE:
|
Apparently there is a streamer for
but the I am a bit lost and have not found anything about it yet.
Apologise for desperately pinging you @jpivarski but maybe you have a hint |
never liked type guessing so this is great! |
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.
feel free to merge as long as tests are passing
So for now I am just forcing it to be Btw. Jerry asked ChatGPT and here is the answer 😆 Here the transcript:
|
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #227 +/- ##
==========================================
+ Coverage 90.11% 90.12% +0.01%
==========================================
Files 18 18
Lines 2124 2127 +3
==========================================
+ Hits 1914 1917 +3
Misses 210 210
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Alight, I added some notes. It's yet unclear how to treat it correctly but for now Let's merge and come back if someone complains `;) |
@Moelf I might need a little bit of help here ;) I realised that the streamer lookup is bugged and I also need to change the order of decisions in
JaggType
. I think that streamer information should have precedence over other methods of type-guess, like matching[*]
in the title etc.Currently we have a "last-resort" lookup in the streamer list of a class, where we take the first element. This was calling for trouble for custom classes which have multiple fields (with possibly different types). See my revelation at #226 (comment)
TL;DR: I realised that
fID
is the index of to the streamer of the parent class' streamer list, so this PR is definitely a bug fix.All the tests pass but two are failing: