-
Notifications
You must be signed in to change notification settings - Fork 21
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(*): prevent conflicts in progress dashboard component #1288
Conversation
Deployed to https://test-deployment-pr-1288.herokuapp.com/ |
…creation # Conflicts: # src/app/features/progress-dashboard-widget/progress-dashboard/progress-dashboard.component.spec.ts
this.data = new ProgressDashboardConfig(this.dashboardConfigId); | ||
this.entityMapper | ||
this.loadConfigFromDatabase().catch(() => |
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.
Is there a reason not to wait for the state to be synced altogether?
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
🎉 This PR is included in version 3.6.2-master.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.6.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.6.2-master.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
The progress dashboard currently creates a new config before the sync is completed which results in a document update conflict whenever a user logs in for the first time.
Visible/Frontend Changes
--
Architectural/Backend Changes