-
Notifications
You must be signed in to change notification settings - Fork 8.5k
fix: Data view creation flyout glitches when the page is accessed from a separate page (#227851) #228749
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
Conversation
…es from onTryESQL causing redraws (227851)
3994942 to
afe824e
Compare
davismcphee
left a comment
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.
Thanks for the contribution @pure-zero! Running CI for now so you can see if there are any failures.
...ns/shared/data_view_management/public/components/index_pattern_table/index_pattern_table.tsx
Outdated
Show resolved
Hide resolved
|
/ci |
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Looks like this was built on the commit previous to the auto commit can we run the ci on this again |
|
Hi @pure-zero! You're right about ESLint - the auto commit should fix this. Could you double check? We can run CI again after fixing this. Thanks! |
Thanks for that @akowalska622 I have updated that now, sorry missed that in the clean up. |
No worries! Running the CI now |
|
/ci |
|
@akowalska622 Can you take another look at this? I am unable to add the required labels I believe. |
|
Of course, on it! Apologies for the delay |
|
@davismcphee could you verify backport label? Thanks! |
|
/ci |
|
@elasticmachine run docs-build |
|
@akowalska622 Where it's just a minor UI bug and low impact, I'd suggest we skip the backports for this one. The risk of introducing a regression in an older branch is probably higher than the value of the fix IMO. I updated the backport label. Also ran the docs build since we'll need it to pass before we can merge. |
|
Sounds good to me, thank you! |
|
/ci |
|
@elasticmachine run docs-build |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
History
|
akowalska622
left a comment
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.
Looks good to me. I checked it out locally and it's working as intended, thanks for the contribution!
|
Thanks for the help getting that in @akowalska622 and @davismcphee |
…m a separate page (elastic#227851) (elastic#228749) elastic#227851 ## Summary Extracts IndexPatternEditor out of IndexPatternTable to avoid state changes A full component rerender is run when onTryESQL state is updated, which causes the flyout animation to be run again <img width="1364" height="733" alt="Screenshot 2025-07-21 at 10 44 41 pm" src="https://github.com/user-attachments/assets/490392cd-4c44-4cf1-8880-8d4e93c547fc" /> Another change could be to have the NoDataViewsPrompt not take onTryESQL as a prop. However, it is intended to be a presentational prop, so that could be a more fundamental change. I would appreciate some input on that. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ania Kowalska <63072419+akowalska622@users.noreply.github.com>
…m a separate page (elastic#227851) (elastic#228749) elastic#227851 ## Summary Extracts IndexPatternEditor out of IndexPatternTable to avoid state changes A full component rerender is run when onTryESQL state is updated, which causes the flyout animation to be run again <img width="1364" height="733" alt="Screenshot 2025-07-21 at 10 44 41 pm" src="https://github.com/user-attachments/assets/490392cd-4c44-4cf1-8880-8d4e93c547fc" /> Another change could be to have the NoDataViewsPrompt not take onTryESQL as a prop. However, it is intended to be a presentational prop, so that could be a more fundamental change. I would appreciate some input on that. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ania Kowalska <63072419+akowalska622@users.noreply.github.com>
#227851
Summary
Extracts IndexPatternEditor out of IndexPatternTable to avoid state changes
A full component rerender is run when onTryESQL state is updated, which causes the flyout animation to be run again
Another change could be to have the NoDataViewsPrompt not take onTryESQL as a prop. However, it is intended to be a presentational prop, so that could be a more fundamental change. I would appreciate some input on that.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.