-
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
[Maps][File upload] fix layer in preview mode shows different results after uploading geojson file when feature-count exceeds ES-search limit #97157
Conversation
… after uploading geojson file when feature-count exceeds ES-search limit
Pinging @elastic/kibana-gis (Team:Geo) |
x-pack/plugins/maps/public/classes/layers/file_upload_wizard/config.tsx
Outdated
Show resolved
Hide resolved
: [ | ||
{ | ||
id: ADD_LAYER_STEP_ID, | ||
label: ADD_LAYER_STEP_LABEL, | ||
}, | ||
]; |
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.
If all layers ultimately end in an "Add layer step", what's the point in overriding this with prereq steps that include an add layer step vs. always including it here as we did before?
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 did this so ClientFileCreateSourceEditor would know when the final step without needing to know about ADD_LAYER_STEP_ID since ADD_LAYER_STEP_ID seemed like an internal detail in AddLayerPanel.
I will revert this change and instead, pass isOnFinalStep to renderWizard since that is the information that is needed by ClientFileCreateSourceEditor. That way, ADD_LAYER_STEP_ID is the final step even when prerequisiteSteps are provided.
First pass looks good. The extra step makes sense to me and it's a nice transition from preview to docs 👍 |
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.
Overall I think this is a nicely improved flow. Some minor comments. Worked well in local tests. lgtm!
- code review
- tested locally in chrome
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
Unknown metric groupsAPI count
API count missing comments
API count with any type
Non-exported public API item count
History
To update your PR or re-run it, just comment with: |
… after uploading geojson file when feature-count exceeds ES-search limit (elastic#97157) * [Maps][File upload] fix layer in preview mode shows different results after uploading geojson file when feature-count exceeds ES-search limit * i18n clean up * review feedback Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
… after uploading geojson file when feature-count exceeds ES-search limit (#97157) (#97325) * [Maps][File upload] fix layer in preview mode shows different results after uploading geojson file when feature-count exceeds ES-search limit * i18n clean up * review feedback Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
fixes #40091
This PR updates the file upload flow.
Previously, the preview layer would automatically switched from file preview to the Elasticsearch document layer when the upload process completed. This can be a very visually jaunting process since the preview may show points while the Elasticasearch document layer may show clusters.
This PR updates the file upload flow to only switch from the file preview to the Elasticsearch document layer after the user clicks "Add as document layer" button to avoid any drastic changes until a user has performed an action and knows why the layer is changing.