Update supervisor's idea table immediately upon scheduling a first meeting #105

Merged
ansv7779 merged 4 commits from first-meeting-feedback into develop 2025-02-13 09:59:34 +01:00

4 Commits

Author SHA1 Message Date
973a41a563 Merge branch 'develop' into first-meeting-feedback
All checks were successful
Deploy to branch.dsv.su.se / deploy (pull_request) Successful in 3m41s
Build and test / build-and-test (push) Successful in 15m49s
Remove branch deployment from branch.dsv.su.se / cleanup (pull_request) Successful in 11s
# Conflicts:
#	core/src/main/java/se/su/dsv/scipro/DataInitializer.java
2025-02-12 15:03:59 +01:00
12badef08b Fix idea table being updated with first meeting information after scheduling
All checks were successful
Deploy to branch.dsv.su.se / deploy (pull_request) Successful in 3m54s
Build and test / build-and-test (push) Successful in 22m49s
What happened was the idea was loaded (the model got attached) without a first meeting, then the first meeting was created separately in a different model. After creating the first meeting the second model had its object updated in place so no call to IModel#setObject was made. Even if it had been called since there was this separation the idea model would not have been updated either way. Implementing #setObject in the FirstMeetingModel (in FirstMeetingPanel) that would update the idea model would not have solved since its #setObject was never called.

To get around this we either have to update the idea models object in place (the chosen solution) or detaching it, forcing a reload from the database that would see the newly created first meeting.
2025-02-10 13:31:54 +01:00
8900909191 Add test-data 2025-02-10 12:46:13 +01:00
d90a373a00 Simplify to get rid of unreachable state 2025-02-10 12:31:15 +01:00