Skip to content
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

Longer normalized values #40

Closed
jcassee opened this issue Apr 27, 2018 · 2 comments
Closed

Longer normalized values #40

jcassee opened this issue Apr 27, 2018 · 2 comments

Comments

@jcassee
Copy link
Contributor

jcassee commented Apr 27, 2018

Sometimes 20 characters is not enough for a value. A datetime with timezone, for example, is rendered as "2018-01-01 12:00:00+ ...". In other cases the value could be best rendered as a multiline string.

It would be nice to be able to influence the reporter in this way.

@h2non
Copy link
Member

h2non commented May 1, 2018

Yeah, I guess that can be increased and even apply a dynamic cut size depending on the value length. E.g: if len(x) < 50 display all else cut to 40 characters.

@sgissinger
Copy link
Contributor

This size has been raised to 50 characters in #64 .
It seems to be enough to have complete datetimes and enough objects string representation to be relevant.

Maybe this issue can be closed for now ?

@h2non h2non closed this as completed Nov 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants