|
|
5e6d8ac487
|
Parse those too
|
2025-01-25 00:58:27 -05:00 |
|
|
|
d5ad727e32
|
that should return a response
|
2025-01-25 00:49:13 -05:00 |
|
|
|
84e7df6c30
|
Add GET endpoint for inactivity-notice-by-id
|
2025-01-23 15:47:30 -05:00 |
|
|
|
b8b5cf3f21
|
oops
|
2024-08-23 01:21:57 -04:00 |
|
|
|
e00b7e8c55
|
KV to D1 migration (this is totally gonna break something)
|
2024-05-12 01:25:46 -04:00 |
|
|
|
c3f89d86db
|
Send webhook notifications for inactivity updates
|
2024-02-18 18:28:02 -05:00 |
|
|
|
43b1f1d136
|
How did this go unnoticed for so long
|
2024-02-15 13:10:57 -05:00 |
|
|
|
e4a0bb4753
|
Generally fix up inactivity notices
|
2023-11-04 22:51:43 -04:00 |
|
|
|
a4eaead08d
|
Flip arguments
|
2023-10-26 11:09:02 -04:00 |
|
|
|
528ba3a755
|
Set approved property in d1 on inactivity closure
|
2023-10-26 10:50:10 -04:00 |
|
|
|
7df177d75c
|
Delete FCM token on inactivity closure
|
2023-10-20 14:00:29 -04:00 |
|
|
|
adde22804a
|
Send notifications on inactivity notice closure
|
2023-10-20 13:56:40 -04:00 |
|
|
|
4adae3af51
|
Set and handle open property on inactivity notices
|
2023-10-20 13:32:03 -04:00 |
|
|
|
3155442796
|
Le formatting fixes
|
2023-10-19 16:50:58 -04:00 |
|
|
|
2fc73a62cc
|
Maybe fix inactivity notices?
|
2023-10-19 16:50:52 -04:00 |
|
|
|
0559877ca4
|
Make POST handler for existing inactivity notice
|
2023-10-19 16:50:48 -04:00 |
|
|
|
dd2d9f2672
|
Greatly reduce repeated code
|
2023-10-19 16:50:48 -04:00 |
|
|
|
6b4f33272f
|
Create PUT handler for inactivity notices
|
2023-10-19 16:50:16 -04:00 |
|
|
|
c295f3e4df
|
Add inactivity deletion endpoint
|
2023-10-19 16:50:15 -04:00 |
|
