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

simplified tabify #19061

Merged
merged 26 commits into from
Aug 30, 2018
Merged

simplified tabify #19061

merged 26 commits into from
Aug 30, 2018

Conversation

ppisljar
Copy link
Member

@ppisljar ppisljar commented May 15, 2018

simplifies tabify:

  • splits are no longer supported, tabify will always produce a flat table
  • rows is now array of row objects, where each column value is a property on this object
  • column values are raw values (no longer field formatted)

all the response handlers are now based on top of this simple tabify.

new table response handler was added which 'emulates' the old table format and is only used by table visualization. Once table visualization gets ported to react this can be removed.

Closes #20197
Closes #22168

QA: No functionality has changed, however every visualization could potentially break due to this as it changes the data format.

Dev-Docs

Custom no data screen

By default Kibana will take care of showing "No data" to the user if no data was retrieved for a visualization. You can disable that behavior by specifying useCustomNoDataScreen: true in your vis type registration. This flag replaces the earlier handleNoData flag due to its confusing name. The handleNoData flag does not have any effect anymore.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@ppisljar ppisljar added WIP Work in progress Feature:Visualizations Generic visualization features (in case no more specific feature label is available) labels May 15, 2018
@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@ppisljar ppisljar added review and removed WIP Work in progress labels Aug 15, 2018
@ppisljar ppisljar requested a review from markov00 August 15, 2018 14:46
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@@ -24,23 +24,27 @@ import { tabifyGetColumns } from './_get_columns';
* Writer class that collects information about an aggregation response and
* produces a table, or a series of tables.
*
* @param {Vis} vis - the vis object to which the aggregation response correlates
* @param {AggConfigs} aggs - the agg configs object to which the aggregation response correlates
* @param {boolean} minimalColumns - setting to false will produce metrics for every bucket
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this needs adjustements to the new parameters partialRows and metricsAtAllLevels now.

*/
function TabbedAggResponseWriter(aggs, opts) {
this.opts = opts || {};
function TabbedAggResponseWriter(aggs, { metricsAtAllLevels = false, partialRows = false }) {
Copy link
Contributor

Choose a reason for hiding this comment

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

function TabbedAggResponseWriter(aggs, { metricsAtAllLevels = false, partialRows = false }) {
->
function TabbedAggResponseWriter(aggs, { metricsAtAllLevels = false, partialRows = false } = {}) {

That way it will also work if the user didn't specify a 2nd parameter at all.

@@ -41,7 +41,7 @@ describe('Vislib Vis Type', function () {
describe('initialization', () => {
it('should set the basic response handler if not set', () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

it should set the **vislib** response handler if not set

Copy link
Contributor

@timroes timroes 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

@elasticmachine
Copy link
Contributor

💔 Build Failed

@ppisljar
Copy link
Member Author

12:55:47    │ERROR [POST http://localhost:9515/session / {"desiredCapabilities":{},"requiredCapabilities":{}}] unknown error: Chrome failed to start: exited abnormally
12:55:47    │        (unknown error: DevToolsActivePort file doesn't exist)

@ppisljar
Copy link
Member Author

retest

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@ppisljar ppisljar merged commit e5a94e7 into elastic:master Aug 30, 2018
ppisljar added a commit to ppisljar/kibana that referenced this pull request Aug 30, 2018
@ppisljar ppisljar deleted the enh/tabifyNewVersion branch August 30, 2018 13:10
ppisljar added a commit that referenced this pull request Aug 31, 2018
@timroes timroes added the release_note:plugin_api_changes Contains a Plugin API changes section for the breaking plugin API changes section. label Sep 4, 2018
@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
Feature:Visualizations Generic visualization features (in case no more specific feature label is available) release_note:plugin_api_changes Contains a Plugin API changes section for the breaking plugin API changes section. review v6.5.0 v7.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants