Debugger::$maxLen not working

[matak]

If I set maxLen=1000 still truncate is set to 150.

"SELECT products.ids as ids,products.type as type,products.sku as sku,products.EAN as EAN,products.producer_id as `produce ... " (1699)

Maybe the problem is here

https://github.com/nette/tracy/blob/master/src/Tracy/assets/BlueScreen/bluescreen.phtml#L136

that no options of truncate is set.

[JanTvrdik]

That is feature. That being said – it may currently not be obvious for programmer to see what is affected by some options and what is not.

[dg]

It affects only function dump()

[JanTvrdik]

More precisely it affects Debugger::dump() and Debugger::barDump(). Dumper::dump() + others are unaffected. Changing Bluescreen options is currently not possible. Not sure whether that is intentional or it was just considered unnecessary.

[matak]

So how you debug longer strings if i can not see them?

[dg]

If I needed to debug longer strings, I would have to implement it, probably in BlueScreen class.

[matak]

sorry for my english

If I needed - means that you suggest me to implement it? or you want to tell me that there is no need to implement it?

if i implemented and nobody is interested to add my pull request so it would not help me

[dg]

Jak ladíte delší řetězce, pokud je nemohu vidět?

(Nijak.) Kdybych to potřeboval, musel bych si to naimplementovat, asi do třídy BlueScreen.

Of course, you can implement it.

[nechutny]

I 've found same "bug". When I 'm debugging some SQL i want to view them full. Tried to set Debugger::$maxLen to bigger size, but no success. It's not only dump() function, but also function arguments at blue screen. I think, that expected behaviour is using $maxLen. So we can change src/Tracy/Dumper.php line 93 from hardcoded value (ugly!) to something like Debugger::$maxLen. I can prepare PR for this.