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

fix: use afterRender to detect dashboard rendered #5970

Merged
merged 1 commit into from
Feb 25, 2025

Conversation

pbenes
Copy link
Contributor

@pbenes pbenes commented Feb 24, 2025

Hidden under enableDashboardAfterRenderDetection feature flag.

Contains fixes for headlines, introduced afterRender method
for Repeater chart.

Note: vis switcher executes only a single visualization and then
relies on executedActions.setDashboardExecutionDone() to initiate
other executions. Moreover, it does it through DashboardInsight so
the mechanism should remain working.

risk: low
JIRA: STL-138


Important

Please, don't forget to run rush change for the commits that introduce new features or significant changes 🙏 This information is used to generate the change log.


Run extended test by pull request comment

Commands can be triggered by posting a comment with specific text on the pull request. It is possible to trigger multiple commands simultaneously.

extended-test --backstop | --integrated | --isolated | --record [--filter <file1>,<file2>,...,<fileN>]

Explanation

  • --backstop The command to run screen tests.
  • --integrated The command to run integrated tests against the live backend.
  • --isolated The command to run isolated tests against recordings.
  • --record The command to create new recordings for isolated tests.
  • --filter (Optional) A comma-separated list of test files to run. This parameter is valid only for the --integrated, --isolated, and --record commands.

Examples

extended-test --backstop
extended-test --integrated
extended-test --integrated --filter test1.spec.ts,test2.spec.ts
extended-test --isolated
extended-test --isolated --filter test1.spec.ts,test2.spec.ts
extended-test --record
extended-test --record --filter test1.spec.ts,test2.spec.ts

@pbenes pbenes requested a review from kandl as a code owner February 24, 2025 13:11
@pbenes pbenes added the do not merge Do not merge this yet label Feb 24, 2025
@pbenes
Copy link
Contributor Author

pbenes commented Feb 24, 2025

extended-test --isolated

Copy link

"extended-test --isolated" started. Check the progress here.

Copy link

❌ "extended-test --isolated" finished with result failure. Check the results here.

@pbenes
Copy link
Contributor Author

pbenes commented Feb 25, 2025

extended-test --isolated

Copy link

"extended-test --isolated" started. Check the progress here.

Copy link

✅ "extended-test --isolated" finished with result success. Check the results here.

@pbenes
Copy link
Contributor Author

pbenes commented Feb 25, 2025

extended-test --integrated

Copy link

"extended-test --integrated" started. Check the progress here.

Copy link

✅ "extended-test --integrated" finished with result success. Check the results here.

@pbenes
Copy link
Contributor Author

pbenes commented Feb 25, 2025

extended-test --isolated

Copy link

"extended-test --isolated" started. Check the progress here.

Copy link

✅ "extended-test --isolated" finished with result success. Check the results here.

@pbenes pbenes force-pushed the pb-afterrender-ff branch 2 times, most recently from ef39633 to 89be2a2 Compare February 25, 2025 08:54
@pbenes pbenes removed the do not merge Do not merge this yet label Feb 25, 2025
@@ -48,19 +50,33 @@ export default class LegacyHeadline extends React.Component<IHeadlineVisualizati
disableDrillUnderline: false,
};

private secondaryItemTitleWrapperRef = createRef<HTMLDivElement>();
private afterRenderGuardTimeoutId;
private afterRenderCalled = false;
Copy link
Contributor

Choose a reason for hiding this comment

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

what it purpose of this guard? never set to true afterRenderCalled

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed, and used the guard

@pbenes pbenes force-pushed the pb-afterrender-ff branch 2 times, most recently from ec96e81 to 350d503 Compare February 25, 2025 10:32
@pbenes
Copy link
Contributor Author

pbenes commented Feb 25, 2025

extended-test --isolated

Copy link

"extended-test --isolated" started. Check the progress here.

Copy link

✅ "extended-test --isolated" finished with result success. Check the results here.

Hidden under enableDashboardAfterRenderDetection feature flag.

Contains fixes for headlines, introduced afterRender method
for Repeater chart.

Note: vis switcher executes only a single visualization and then
relies on executedActions.setDashboardExecutionDone() to initiate
other executions. Moreover, it does it through DashboardInsight so
the mechanism should remain working.

risk: low
JIRA: STL-138
@pbenes
Copy link
Contributor Author

pbenes commented Feb 25, 2025

extended-test --isolated

Copy link

"extended-test --isolated" started. Check the progress here.

Copy link

✅ "extended-test --isolated" finished with result success. Check the results here.

@ivanmjartan ivanmjartan merged commit ffdebe4 into master Feb 25, 2025
21 checks passed
@ivanmjartan ivanmjartan deleted the pb-afterrender-ff branch February 25, 2025 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants