-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
React component support fork 2 #64224
Conversation
Pinging @elastic/kibana-app-arch (Team:AppArch) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
please provide description and link to an issue. why not move the ExpressionRendering inside expression service with this PR already, seems it should be a simple change from here on ? |
@ppisljar it is what this PR does, it moves |
@elasticmachine merge upstream |
💔 Build Failed
Failed CI Steps
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM
Can this be closed? looks stale? I'm going to remove 7.9.2 label on it anyhow. |
Summary
Partially addresses #59744
This PR moves
ExpressionRenderHandler
(renamed toExpressionRendering
) into expressions services. This will enable subsequently to move expressions React component andExpressionLoader
to the expression service, too.ExpressionRenderHandler
toExpressionRendering
.ExpressionRendering
to/common
folder.uiState
handling: Add ability to pass data to expression renderers #64420Checklist
Delete any items that are not applicable to this PR.
For maintainers