to me the font size looks very small. and a lot of unused blank space.

Nice! How would this work for something like "disk size" or strings that may have many values? Is a scrollbar added, or does the page get very long?

to me the font size looks very small. and a lot of unused blank space.

I'm going to add the description for each field, I think @mtojek is working to add the reach parameter description field into the API.

I think @mtojek is working to add the reach parameter description field into the API.

Please file an issue for this, so we don't forget about it.

• list(strings) can be rendered as labels/tags

Good one 👍

• as we don't know what is inside string values, maybe we should wrap them with code tags

I don't see how this would be better 🤔

• consider adding all table headers (value, count). The last column looks like SQL injection...

It does not look good, it was on the first version of the design but was removed, but I will take a look again o this option

• for options: [ ], can you check if name property is exposed instead of the value? It is better to show US (Virginia) instead of eastus.

Makes total sense 👍

• booleans can be rendered as some icons instead of true/false

Totally agree 👍

• URLs could be detected and replaced with links

Sounds good 👍

@mtojek here is the issue: #8907

for options: [ ], can you check
if name property is exposed instead of the value? It is better to show US (Virginia) instead of eastus.

@BrunoQuaresma, we also have an optional display_name, and that would be better to show instead of name. fallback to name if display_name does not exist.

@mtojek suggestions applied:

Related: #8944

With updates: