Bug: Columns not lining up with their headers if initially collapsed

edited August 2022

It seems there is a problem when dumping collections objects with multiple columns when initially collapsed to the 0th level. After expanding, all cells are rendered within the first column:

new object[]
    new { Foo = "foo", Bar = "bar" },
    new { A = "a", B = "b", C = "c" },
}.Dump(collapseTo: 0);

I initially thought this was for heterogeneous collections, but it looks like it happens to any collection of objects with multiple columns.

If not collapsed, it seems to render normally as expected.

Linqpad v7.4.8 (x64)
.net core 6.0.7


Sign In or Register to comment.