-
Notifications
You must be signed in to change notification settings - Fork 19
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
cleanup_unserializable results in weird handling of unserializable user_properties #12
Labels
bug
Something isn't working
Comments
@nicoddemus i propose we switch to a own json encoder that replaces single broken objects with
|
RonnyPfannschmidt
added a commit
to RonnyPfannschmidt/pytest-reportlog
that referenced
this issue
May 2, 2023
instead of str this creates a difference in logged data warning messages needed a change instead of toplevel values, only the sub-object is affected
To be clear, would you expect this? "user_properties": [
[
"hello",
"{'mars', 'world'}"
]
], @RonnyPfannschmidt do you mean something like this? "user_properties": [
[
"hello",
{"$unserializable": "{'mars', 'world'}"}
]
], |
@nicoddemus see the draft mr |
Ahh I see, so #35 will output: "user_properties": [
[
"hello",
{"$no-json": "{'mars', 'world'}"}
]
], What do you think @The-Compiler ? |
RonnyPfannschmidt
added a commit
to RonnyPfannschmidt/pytest-reportlog
that referenced
this issue
May 3, 2023
instead of str this creates a difference in logged data warning messages needed a change instead of toplevel values, only the sub-object is affected
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This file:
results in the following reports (pretty printed for readability):
Note the different storage of
user_properties
:i.e. if an user property value is unserializable, the entire value gets turned into a string, rather than turning that specific property into one.
The text was updated successfully, but these errors were encountered: