-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Adding in browser info to the report-info drawer #26307
Adding in browser info to the report-info drawer #26307
Conversation
@@ -41,6 +41,7 @@ const schema = { | |||
}, | |||
} | |||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this makes much a difference since we're likely updating an existing index in current installations. Is there more here that I need to follow up with?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additions to the data model should be fine as long as it is released in a minor version (not a patch). It'll be worthwhile to test an upgrade scenario: create some reports in 6.5.x and then upgrade to 6.6.x, and check out the browser_type
behavior.
💚 Build Succeeded |
@@ -145,6 +144,10 @@ export class ReportInfoButton extends Component<Props, State> { | |||
title: 'Status', | |||
description: get(info, 'status', NA), | |||
}, | |||
{ | |||
title: 'Browser Type', | |||
description: get(info, 'browser_type', NA), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a huge deal, but it would be nice if this said unknown
if the report in the listing is a PDF report that was created in an older version of Kibana where the browser_type
isn't available. If the report is a CSV job, it should say n/a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, great point, forgot about our old friend CSV -- will adjust
I don't want this to land in a patch release... are patch releases branched off of their respective minor tags? |
For it to land in a patch release, someone would need to backport it to the 6.5 branch, which we will not do. After this is merged to master (7.0), I'll ask you to backport it to 6.x, which is versioned 6.6.0. I'm also adding version labels to this PR for you. I sometimes accidentally overlook the need for version labels in PRs when I review them - sorry about that :) |
Awesome! I'll try and add these myself as time goes on. :dank: |
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sent a suggestion. I haven't used this Github feature before, so not sure it's going to work!
Nice! That's a pretty cool feature. Saves me from going back and forth between the editor + GH |
const config = server.config(); | ||
const queueConfig = config.get('xpack.reporting.queue'); | ||
const browserType = config.get('xpack.reporting.capture.browser.type'); | ||
const browserType = server.config().get('xpack.reporting.capture.browser.type'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will fix this dupe
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Reviewed the code and tested PDF and CSV reports
Summary
Adds in browser-type to the reporting info side-panel. Will tackle the next TODO once I can figure out a good way to source what kicked off the report.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.[ ] This was checked for cross-browser compatibility, including a check against IE11[ ] Documentation was added for features that require explanation or tutorials[ ] This was checked for keyboard-only and screenreader accessibility