Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Lens] "Show defaults of error" doesn't become "Hide details of error" once opened #95956

Closed
ghudgins opened this issue Mar 31, 2021 · 1 comment · Fixed by #96605
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens good first issue low hanging fruit Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@ghudgins
Copy link

Kibana version:
7.13-SNAPSHOT

Elasticsearch version:
7.13-SNAPSHOT

Original install method (e.g. download page, yum, from source, etc.):
Cloud deployment

Describe the bug:

In Lens, the text "Show details of error" functions properly but the string is inaccurate once the details are shown.

Steps to reproduce:

  1. In Lens, create an invalid runtime field
  2. Drag the field, producing Lens error state
  3. Click "Show details of error

Result: the details show, but the button says "Show details of error"

Expected behavior:

the details show, but the button says "Hide details of error" indicating the details can be hidden

Screenshots (if relevant):
image

@ghudgins ghudgins added bug Fixes for quality problems that affect the customer experience Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Mar 31, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens good first issue low hanging fruit Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants