-
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
[Vega] Maps still experimental #79114
Conversation
@stratoula @timroes I have one concern around that task. In vega vis we cannot understand from which place visualization was opened (from dashboard or from vis_editor). It's a bad thing cause by default that message will be shown on dashboard too. Yes, user can hide it using the hideWarnings configuration field but anyway not sure that we want to see it by default. Any ideas? |
src/plugins/vis_type_vega/public/components/experimental_map_vis_info.tsx
Outdated
Show resolved
Hide resolved
src/plugins/vis_type_vega/public/components/experimental_map_vis_info.tsx
Outdated
Show resolved
Hide resolved
@alexwizp I agree, this is not very good. Have you tried to add the Callout outside the visualization container? |
@@ -44,7 +44,7 @@ interface CommonBaseVisTypeOptions { | |||
useCustomNoDataScreen?: boolean; | |||
inspectorAdapters?: Adapters | (() => Adapters); | |||
isDeprecated?: boolean; | |||
getDeprecationMessage?: (vis: Vis) => ReactElement<{}>; | |||
getInfoMessage?: (vis: Vis) => ReactElement<{}>; |
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.
@timroes @stratoula @sulemanof Probably we can use getDeprecationMessage
to archive out goal.
But name should be more generic.
One more point if we decide to go with it, in this case we should parse spec twice =( But probably it's not a problem
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.
I am fine with this approach 🙂
@elasticmachine merge upstream |
Pinging @elastic/kibana-app (Team:KibanaApp) |
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.
I have tested it locally, it works as expected. Code LGTM
); | ||
|
||
return ( | ||
<I18nProvider> |
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.
The provider is extra here.
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.
LGTM
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]@kbn/optimizer bundle module count
async chunks size
page load bundle size
History
To update your PR or re-run it, just comment with: |
* [Vega] Maps still experimental * fix TS issues * cleanup Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Closes: #78267
Summary
Adding an experimental warning when user works on a vega map
Checklist
Delete any items that are not applicable to this PR.
For maintainers