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

Pipeline field formatting #28746

Merged
merged 15 commits into from
Jan 18, 2019
Merged

Conversation

ppisljar
Copy link
Member

@ppisljar ppisljar commented Jan 15, 2019

Summary

handling field formatting in the expressions

all visualizations now get formatting options passed in as part of the configuration

  • vislib charts no longer require aggConfig information
  • legacy response handler now only does table splitting and doesn't require aggConfigs
  • point series response handler now builds directly on top of tabify table and doesn't require aggConfigs
  • hierarchical response handler now builds directly on top of tabify table and doesn't require aggConfigs

bottom line: aggConfig is no longer necesarry in any response handlers or any visualization.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

@ppisljar ppisljar added review Feature:ExpressionLanguage Interpreter expression language (aka canvas pipeline) Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jan 15, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💔 Build Failed

Copy link
Member

@lukeelmers lukeelmers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ppisljar I feel like I just ran a marathon (In a good way!) 😉

Added a handful of comments: some nits, some questions on structure, and only a couple items that are potential buggy edge cases. Overall though, this is great -- it all feels way cleaner without AggConfigs hanging around everywhere 😄

I've also done some initial testing locally (Chrome OSX) and so far not noticing any obvious issues.

Ping me if you want to sync on any of these notes!

src/ui/public/vis/vis_filters.js Show resolved Hide resolved
src/ui/public/utils/brush_event.js Outdated Show resolved Hide resolved
src/ui/public/vis/response_handlers/legacy.js Show resolved Hide resolved
src/ui/public/vis/response_handlers/vislib.js Outdated Show resolved Hide resolved
src/ui/public/vislib/lib/dispatch.js Show resolved Hide resolved
@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Member

@markov00 markov00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM. Tested the main functionalities, fiters and tooltips.
I've left just a minor comment

} else {
title = aggConfig.makeLabel();
}
if (!isPercentageMode) value = this._getFormattedValue(formatter, value, 'html');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you move this as the else of the previous if statement?

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Feature:ExpressionLanguage Interpreter expression language (aka canvas pipeline) review Team:Visualizations Visualization editors, elastic-charts and infrastructure v7.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants