-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[APM] Convert DB statement code box to EuiCode #76849
Labels
enhancement
New value added to drive a business result
Team:APM
All issues that need APM UI Team support
Comments
formgeist
added
Team:APM
All issues that need APM UI Team support
enhancement
New value added to drive a business result
labels
Sep 7, 2020
Pinging @elastic/apm-ui (Team:apm) |
14 tasks
EuiCodeBlock supports line numbers as of elastic/eui#4993, so we can replace the code we're using with that now. |
Not sure that line numbers was a requirement to get this replaced? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
botelastic
bot
added
the
stale
Used to mark issues that were closed for being stale
label
Mar 21, 2022
botelastic
bot
removed
the
stale
Used to mark issues that were closed for being stale
label
Mar 21, 2022
boriskirov
added a commit
that referenced
this issue
Apr 4, 2022
* [APM] Convert DB statement code box to EuiCode Closes #76849 * added a target_blank attribute to the link * added target attribute and removed more code from the db statement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New value added to drive a business result
Team:APM
All issues that need APM UI Team support
Summary
The current database statement is presented in a custom code block component, but we should move to use
EuiCode
(EUI example) for consistent look and feel in Kibana.We have some challenges with the Kibana dark mode, which would also be resolved by changing to the new component.
One requirement is that we're able to pass the same syntax highlighting that we currently have in the code component.
The text was updated successfully, but these errors were encountered: