Skip to content

Conversation

@raulbob
Copy link
Contributor

@raulbob raulbob commented Jun 24, 2025

The bug was caused by HealthConditionsForm not properly checking if the form was dirty. This has been fixed by ensuring that the form checks its dirty state before triggering events.

  • HealthConditionsForm now correctly checks if the form is dirty before triggering save or discard changes events.
  • CommitDiscardWrapperComponent added HealthConditionsForm to the list of components that can be checked for dirty state.

The bug was caused by `HealthConditionsForm` not properly checking if the form was dirty.
This has been fixed by ensuring that the form checks its dirty state before triggering events.

- `HealthConditionsForm` now correctly checks if the form is dirty before triggering save or discard changes events.
- `CommitDiscardWrapperComponent` added `HealthConditionsForm` to the list of components that can be checked for dirty state.
@raulbob raulbob linked an issue Jun 24, 2025 that may be closed by this pull request
@raulbob raulbob merged commit 54c7524 into development Jun 26, 2025
5 of 8 checks passed
@raulbob raulbob deleted the bugfix-13442_wrongly_asked_save_discard_changes branch June 26, 2025 17:00
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.

Case Form - Wrongly asked to save or discard changes

3 participants