Ceph » mgr » Dashboard

This has something to do how our key value table component handles arrays in side objects. It can handle JSON objects but if you have an array inside it it will stringify it's content, as the table doesn't know how to proceed here as it has now clue what the column should be named than.

Matcher.0.name : value

would be an idea here... but if you would do that you would end up with 3*Matchers more columns and I'm not sure if that would be a nicer view.

Stephan Müller wrote:

This has something to do how our key value table component handles arrays in side objects. It can handle JSON objects but if you have an array inside it it will stringify it's content, as the table doesn't know how to proceed here as it has now clue what the column should be named than.

Matcher.0.name : value

would be an idea here... but if you would do that you would end up with 3*Matchers more columns and I'm not sure if that would be a nicer view.

Yeah. How about setting Matchers as a separate division inside the Details with the heading "Matchers" ofcourse, and then separating each Matchers into its own rows. It wont make a big difference or neither a solution to this bug but it would reduce confusion when there are more than 1 matchers as it would be in separate columns.

That would be a fine solution for this bug - as the table used provides an attribute to hide specific attributes :)