https://bz.apache.org/bugzilla/show_bug.cgi?id=63620

--- Comment #14 from Felix Schumacher <felix.schumac...@internetallee.de> ---
(In reply to Vladimir Sitnikov from comment #13)
> > Right, but it is in the calculation of the width of lines to break them 
> > apart, so it would still be helpful to try to pretty print the large json 
> > structure (if it shortens the lines), don't you think?
> 
> 1) An option to pretty-print based on the content type makes sense. However
> it might "defeat" regular expressions because "user-visible" json would be
> different from the one that came from the network.
> However I do support the idea of pretty-printing by default

I didn't think about pretty printing by us, but by the user (at least in this
case), but we could think about it.

> 
> 2) Even though we have content type, it is not always right. For instance,
> they might sent the data as text/plain, and we have very little clue on how
> to pretty-print.

right. No idea here, we could try to guess the content, but I am pretty sure
this would be a bad idea.

> 
> 3) We might want to implement an option to "forcibly add newlines" for lines
> exceeding N characters. A plus would be to put that newlines in-between word
> breaks so it won't tear words. That might be a decent workaround.

As kind of a fallback pretty printer? That could work (with the addition of
soft and hard breaks in the case there are no word boundaries)

> 
> 4) It might be a Java-related issue. For instance, they say
> https://bugs.openjdk.java.net/browse/JDK-4202291 is fixed in Java 6
> So it might be JMeter code is doing something wrong. We might want to
> analyze what is causing that slowness.
> For instance, what if we limit "the maximum width" of the textview? Would it
> influence text wrapping algorithm?

Or the fix has not been implemented or re-surfaced? There is mentioned that
adding a newline to the text would be a workaround.

@Frederic could you try to add a newline at the end of your data?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to