-
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
[ui/agg_response/tabify] -> TypeScript & Jest & Shim #57394
Labels
Comments
lukeelmers
added
Feature:Aggregations
Aggregation infrastructure (AggConfig, esaggs, ...)
Team:AppArch
Feature:NP Migration
labels
Feb 11, 2020
Pinging @elastic/kibana-app-arch (Team:AppArch) |
12 tasks
alexwizp
added a commit
to alexwizp/kibana
that referenced
this issue
Feb 16, 2020
[ui/agg_response/tabify] -> TypeScript & Jest & Shim Part of elastic#57394
@lukeelmers @alexwizp Would you mind adding, for the record, a short description to this issue of what tabify is? |
@lizozom Sure thing, just updated the description -- let me know if this helps. Most people know what tabified data looks like, but perhaps just don't know that the name "tabify" was attached to it :) |
alexwizp
added a commit
that referenced
this issue
Feb 20, 2020
* [ui/agg_response/tabify] -> TypeScript & Jest & Shim [ui/agg_response/tabify] -> TypeScript & Jest & Shim Part of #57394 * fix CI * move tabify into new folder * TypeScript _bucket.js * rename _buckets -> bucket * fix CI * tabify.test.js -> tabify.test.ts * tabify.js -> tabify.ts * fix JEST * Update src/legacy/core_plugins/data/public/search/tabify/types.ts Co-Authored-By: Luke Elmers <lukeelmers@gmail.com> * fake_hierarchical_data.js -> fake_hierarchical_data.ts * TimeRange -> TabbedRangeFilterParams Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
alexwizp
added a commit
to alexwizp/kibana
that referenced
this issue
Feb 20, 2020
* [ui/agg_response/tabify] -> TypeScript & Jest & Shim [ui/agg_response/tabify] -> TypeScript & Jest & Shim Part of elastic#57394 * fix CI * move tabify into new folder * TypeScript _bucket.js * rename _buckets -> bucket * fix CI * tabify.test.js -> tabify.test.ts * tabify.js -> tabify.ts * fix JEST * Update src/legacy/core_plugins/data/public/search/tabify/types.ts Co-Authored-By: Luke Elmers <lukeelmers@gmail.com> * fake_hierarchical_data.js -> fake_hierarchical_data.ts * TimeRange -> TabbedRangeFilterParams Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
alexwizp
added a commit
to alexwizp/kibana
that referenced
this issue
Feb 21, 2020
* [ui/agg_response/tabify] -> TypeScript & Jest & Shim [ui/agg_response/tabify] -> TypeScript & Jest & Shim Part of elastic#57394 * fix CI * move tabify into new folder * TypeScript _bucket.js * rename _buckets -> bucket * fix CI * tabify.test.js -> tabify.test.ts * tabify.js -> tabify.ts * fix JEST * Update src/legacy/core_plugins/data/public/search/tabify/types.ts Co-Authored-By: Luke Elmers <lukeelmers@gmail.com> * fake_hierarchical_data.js -> fake_hierarchical_data.ts * TimeRange -> TabbedRangeFilterParams Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
alexwizp
added a commit
that referenced
this issue
Feb 21, 2020
* [ui/agg_response/tabify] -> TypeScript & Jest & Shim [ui/agg_response/tabify] -> TypeScript & Jest & Shim Part of #57394 * fix CI * move tabify into new folder * TypeScript _bucket.js * rename _buckets -> bucket * fix CI * tabify.test.js -> tabify.test.ts * tabify.js -> tabify.ts * fix JEST * Update src/legacy/core_plugins/data/public/search/tabify/types.ts Co-Authored-By: Luke Elmers <lukeelmers@gmail.com> * fake_hierarchical_data.js -> fake_hierarchical_data.ts * TimeRange -> TabbedRangeFilterParams Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Luke Elmers <lukeelmers@gmail.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
In the legacy world, we had multiple response handlers. Their job is basically to take the output from a request handler and convert the data into a shape that is useful for a visualization. Visualization developers could register their own request/response handlers, and specify which ones the vis should use.
With the move to an expressions-backed visualizations infrastructure, our internal usage of request/response handlers has been greatly simplified: everything uses the
esaggs
function, which comes with thecourier
(default) request handler baked in, and thetabify
(default) response handler. Vis developers can still register custom request/response handlers, but there is no need for us to provide these out of the box in kibana anymore.tabify
(likecourier
) is just a legacy name for a response handler that transforms a response into tabular data. Something along these lines:Steps to migrate
src/legacy/ui/public/agg_response/tabify
:prototype
based classes to use ES6 class syntaxsrc/legacy/core_plugins/data/public/search/aggs/agg_response
ui/agg_response/tabify
(we can update imports later once it moves to NP along with the rest ofagg_types
)The text was updated successfully, but these errors were encountered: