[Discover] Fix doc viewer table columns#113124
Conversation
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
|
ACK, will review |
|
@elasticmachine merge upstream |
There was a problem hiding this comment.
this would fix the issue 👍 . however there's one thing I'd like to discuss. So when you have just short filenames and a very broad screen, there's lots of whitespace with this approach:
the alternative solution would be to assign a min width to the fieldname column like this:
.kbnDocViewer__tableRow td:nth-child(2) {
min-width: 108px;
}
Then it would look like this:

More space for the value which I think is more imortant in this case
WDYT dear @elastic/kibana-design
Here's some testdata
POST testdata/_doc/1
{
"veryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.key": "shortvalue"
}
POST testdata/_doc/2
{
"shortkey": "veryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.key"
}
POST testdata/_doc/3
{
"veryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.key": "veryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.keyveryvery.very.very.very.veryvery.veryveryvery.very.veryvery.veryvery.very.veryvery.very.very.very.very.very.veryveryvery.long.key"
}
|
I like the solution of having |
|
@elasticmachine merge upstream |
I also like the approach you're proposing here. Let's just remember to use Eui variables to get the pixel value @dmitriynj if you could add some quick before/after screenshots to these PRs it would be super useful when reviewing. |
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @dmitriynj |
| font-family: $euiCodeFontFamily; | ||
|
|
||
| // set min-width for each column except actions | ||
| .euiTableRowCell:nth-child(n+2) { |
There was a problem hiding this comment.
TIL you can do something like n+2 nice!
kertal
left a comment
There was a problem hiding this comment.
LGTM, tested a-la-carte with Firefox, Chrome, Safari. Thx for teaching me advanced CSS 🙏
* [Discover] fix doc viewer table columns * [Discover] apply suggestions * [Discover] apply suggestion * [Discover] fix action column * [Discover] do not apply min-width to actions column Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Discover] fix doc viewer table columns * [Discover] apply suggestions * [Discover] apply suggestion * [Discover] fix action column * [Discover] do not apply min-width to actions column Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
|
Is it possible this broke See https://github.com/elastic/kibana/pull/113550/checks?check_run_id=3769108058 |
|
Sorry, your file appearing may have been a false flag, currently suspecting #113443 |
* [Discover] fix doc viewer table columns * [Discover] apply suggestions * [Discover] apply suggestion * [Discover] fix action column * [Discover] do not apply min-width to actions column Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Discover] fix doc viewer table columns * [Discover] apply suggestions * [Discover] apply suggestion * [Discover] fix action column * [Discover] do not apply min-width to actions column Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>


Summary
Fixes #112966
Checklist
Risk Matrix
Delete this section if it is not applicable to this PR.
Before
After
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers