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

[Canvas] XY. Step 3. Move XY functions and renderer from vis_types to chart_expressions. #112425

Closed

Conversation

Kuznietsov
Copy link
Contributor

@Kuznietsov Kuznietsov commented Sep 16, 2021

Completes part of #110430 and #101377

Step 3. XY. Move XY functions and renderer from vis_types to chart_expressions.

Further steps have been performed at this PR:

  • the expression renderer and functions have been moved to a separate expressionXy plugin;
  • vis_type editor configuration has been left at visTypeXy plugin;
  • types have been moved to the related plugin.

Kuznietsov and others added 19 commits September 21, 2021 18:12
…xy_chart_step_2

# Conflicts:
#	src/plugins/vis_types/vislib/public/vislib/helpers/point_series/_add_to_siri.ts
#	src/plugins/vis_types/xy/public/config/get_aspects.ts
#	src/plugins/vis_types/xy/public/config/get_axis.ts
#	src/plugins/vis_types/xy/public/config/get_config.ts
#	src/plugins/vis_types/xy/public/expression_functions/xy_vis_fn.ts
#	src/plugins/vis_types/xy/public/services.ts
#	src/plugins/vis_types/xy/public/to_ast.ts
#	src/plugins/vis_types/xy/public/types/param.ts
#	src/plugins/vis_types/xy/public/utils/accessors.tsx
#	src/plugins/vis_types/xy/public/vis_component.tsx
#	src/plugins/visualizations/common/expression_functions/xy_dimension.ts
# Conflicts:
#	src/plugins/chart_expressions/expression_xy/common/expression_functions/xy_vis_fn.ts
#	src/plugins/chart_expressions/expression_xy/common/utils/accessors.tsx
#	src/plugins/chart_expressions/expression_xy/public/vis_component.tsx
#	src/plugins/vis_types/xy/public/services.ts
@Kuznietsov
Copy link
Contributor Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

merge conflict between base and head

@Kuznietsov
Copy link
Contributor Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @Kunzetsov

@@ -92,6 +93,7 @@ export class AggConfig {
public parent?: IAggConfigs;
public brandNew?: boolean;
public schema?: string;
public buckets?: TimeBuckets;
Copy link
Member

Choose a reason for hiding this comment

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

why was this added ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If I remember right, I've done it for this case:

const { esUnit, esValue } = xAgg.buckets.getInterval();

That field exists at theAggConfig instance.

@Kuznietsov Kuznietsov closed this Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed Feature:Canvas impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort release_note:feature Makes this part of the condensed release notes Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants