Skip to content

Pipeline field formatting - #28746

Merged
ppisljar merged 15 commits into
elastic:masterfrom
ppisljar:pipeline/fieldFormatting
Jan 18, 2019
Merged

ppisljar merged 15 commits into
elastic:masterfrom
ppisljar:pipeline/fieldFormatting

Conversation

@ppisljar

@ppisljar ppisljar commented Jan 15, 2019 •

Copy link
Copy Markdown
Contributor

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 Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t// labels Jan 15, 2019
@elasticmachine

Copy link
Copy Markdown
Contributor

Pinging @elastic/kibana-app

@elasticmachine

Copy link
Copy Markdown
Contributor

💔 Build Failed

@elasticmachine

Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@elasticmachine

Copy link
Copy Markdown
Contributor

💔 Build Failed

@lukeelmers lukeelmers left a comment

Copy link
Copy Markdown
Contributor

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!

Comment thread src/ui/public/visualize/loader/pipeline_helpers/build_pipeline.ts Outdated
Comment thread src/ui/public/visualize/loader/pipeline_helpers/utilities.ts Outdated
Comment thread src/ui/public/vis/vis_filters.js
Comment thread src/ui/public/utils/brush_event.js Outdated
Comment thread src/ui/public/vis/response_handlers/legacy.js
Comment thread src/ui/public/vis/response_handlers/vislib.js Outdated
Comment thread src/ui/public/vislib/lib/dispatch.js
Comment thread src/ui/public/visualize/loader/pipeline_helpers/build_pipeline.ts Outdated
@elasticmachine

Copy link
Copy Markdown
Contributor

💔 Build Failed

@elasticmachine

Copy link
Copy Markdown
Contributor

💔 Build Failed

@elasticmachine

Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@markov00 markov00 left a comment

Copy link
Copy Markdown
Contributor

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
Copy Markdown
Contributor

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
Copy Markdown
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 Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t// v7.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants