-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add explicit serialization / deserialization to the JsonReporter
#7077
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
Add explicit serialization / deserialization to the JsonReporter
#7077
Conversation
8682180
to
599e9bc
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Pull Request Test Coverage Report for Build 2581426689
💛 - Coveralls |
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.
@Pierre-Sassoulas What is the bug/issue we're trying to solve here?
The goal is to be able to use the message object in the primer instead of a complicated to type dict from the JSON reporter. I identified the issue of confidence and abspath that were lost in the reporting thanks to this. |
Should we consider adding those? Adding new keys to a JSON result shouldn't really break anything right? |
It's a breaking change depending on the implementation ? Say if someone loop on it and try to assign each value to something and it error on unknown value. |
Hmm yeah. We really should provide a |
Silly me, we just have to add a JsonReporter and deprecate the old one ? |
Yeah, but we also need to fix some of the issues that are currently in the beta of |
Hmm ok. Seems we can deal with it later and merge this one then ? |
Well, this is a bit of a handicapped solution. I'd prefer tackling the actual problem, but if you don't have the time for that now I guess this should would be okay? |
I'm not trying to fix the missing confidence / abspath in the json right now, it's just an issue I realized existed while doing what's necessary to use |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
92e336f
to
5a6e76f
Compare
This comment has been minimized.
This comment has been minimized.
9e1c6fc
to
eb2e20c
Compare
This comment has been minimized.
This comment has been minimized.
@DanielNoord can you review this again please ? I added the typed dict :) I have multiple PR ready as follow-up but I don't want to put too much into this one. |
TypedDict is not available in some python version this is why i added it in the type checking guard. |
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.
I pushed some changes which were a bit hard to suggest using the interface.
Let's make the types of the serialisation more explicit and add types of we need to.
Whenever typing stuff is unavailable on older versions we tend to put those under |
593a5ca
to
d967926
Compare
Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
75576dc
to
0464370
Compare
🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉 This comment was generated for commit 0464370 |
Type of Changes
Description
Necessary for Refs #7000