-
Notifications
You must be signed in to change notification settings - Fork 12
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
Kalenteri: Tieto jos muokattu lapsen tulo/lähtöaikaa henkilökunnan toimesta #6122
Conversation
kechpaja-at-gofore
commented
Dec 13, 2024
•
edited
Loading
edited
4e157d4
to
ccf84d4
Compare
d4a9e79
to
5da36be
Compare
@@ -957,22 +963,31 @@ private data class ReservationTimesForDate( | |||
val date: LocalDate, | |||
val startTime: LocalTime?, | |||
val endTime: LocalTime?, | |||
val createdAt: HelsinkiDateTime, | |||
val createdBy: EvakaUser, // TODO should these be modified_by instead? | |||
val staffCreated: Boolean, |
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.
Tämä erillinen staffCreated
flagin tulisi poistaa varauksien ja poissaolomerkintöjen API palautuksista nyt kun front-endiin asti tulee tieto EvakaUser
ista. Sitten tämän aikaisemmin SQL:ässä tehdyn vertailun 'staffCreated', eu.type <> 'CITIZEN'
voisi tehdä frontissa:
staffModified
-> modifiedBy.type != 'CITIZEN'
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.
Tai sitten jos halutaan, että pystytään erottamaan kuntalaisen luoma, mutta henkilökunnan muokkaama merkintä sellaisesta merkinnästä joka on henkilökunnan luoma, niin nuo createdBy
ja createdAt
voisi muuttaa modified*
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.
Hmm.
Voisin kyllä muuttaa createdAt
ja createdBy
modified
-kentiksi.
Tuon staffCreated-muutoksen suhteen pitää kuitenkin ehkä miettiä, onko se oikeasti muuttamisen arvoista, erityisesti tämän vetopyynnön osana. Olen samaa mieltä, että sen olisi voinut tehdä eri tavalla alun perin, mutta on myös se argumentti, että nyt kun se on noin, pitää olla konservatiivinen sen suhteen, tai ainakin erottaa muutoksia tosi huolellisesti.
frontend/src/employee-frontend/components/unit/unit-reservations/ChildDayAttendance.tsx
Outdated
Show resolved
Hide resolved
frontend/src/employee-frontend/components/unit/unit-reservations/ChildDayAttendance.tsx
Outdated
Show resolved
Hide resolved
frontend/src/employee-frontend/components/unit/unit-reservations/ChildDayReservation.tsx
Outdated
Show resolved
Hide resolved
...rationTest/kotlin/fi/espoo/evaka/reservations/ReservationControllerCitizenIntegrationTest.kt
Outdated
Show resolved
Hide resolved
...rationTest/kotlin/fi/espoo/evaka/reservations/ReservationControllerCitizenIntegrationTest.kt
Outdated
Show resolved
Hide resolved
1bd8055
to
d70433a
Compare
service/src/main/kotlin/fi/espoo/evaka/reservations/AttendanceReservationController.kt
Outdated
Show resolved
Hide resolved
service/src/main/kotlin/fi/espoo/evaka/reservations/AttendanceReservationController.kt
Outdated
Show resolved
Hide resolved
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.
Tuon yhden ylimääräisen staffModified
flagin voisi vielä poistaa, muuten OK