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

Alter alert subscription causing the vue application to silently crash #1301

Conversation

cstns
Copy link
Contributor

@cstns cstns commented Sep 17, 2024

Description

The alerts service was subscribing in on the mounted lifecycle method in the Baseline.vue component (which is inherited by all existing layouts) before the UiNotification child component which it acted upot managed to properly mount.

Updated the lifecycle flow in order to preserve lifecycle consistency between parent/child components by forcing the alerts service to subscribe only after the UiNotification components get's mounted properly.

Related Issue(s)

closes #747

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

  • Includes a DB migration? -> add the area:migration label

@cstns cstns requested a review from joepavitt September 17, 2024 11:20
@cstns cstns self-assigned this Sep 17, 2024
@joepavitt joepavitt merged commit 7ed2420 into main Sep 17, 2024
1 of 2 checks passed
@joepavitt joepavitt deleted the 747_fix-ws-reactivity-caused-by-incorrect-component-lifecycle-mount-order branch September 17, 2024 13:11
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.

ui-template nodes not receiving messages after network disconnection/recovery.
2 participants