Update todos

facts.md

@@ -1,10 +1,21 @@
 # DO NOT TOUCH; ONLY HUMAN ALLOWED
 
-
 210 av 480 dagar kvar totalt
 Du: 139 dagar kvar
 Annan förälder: 71 dagar kvar
 
+days left:
 Nivå	            Du	Annan förälder
 Sjukpenningnivå 	94 	26 
-Lägstanivå 	        45 	45
+Lägstanivå 	        45 	45
+
+
+Du kan föra över
+84 dagar på sjukpenningnivå
+45 dagar på lägstanivå
+
+Annan förälder kan föra över
+26 dagar på sjukpenningnivå
+45 dagar på lägstanivå
+
+39 av 60 dubbeldagar kvar efter ansökan

new-todo.md

@@ -3,8 +3,9 @@
 ## High prio
 
 - Check how the "Förskolans planeringsdagar per år" is used: Automatically just removed from the count?
-    This should be a per year "how many did you take" so that we also know the true number each year
+    - This should be a per year "how many did you take" so that we also know the true number each year
     to better understand how many days might go lost.
+    - This also needs to be displayed better in the overview.
 
 - Clicking the Ledig/Arbetsdag in the list of all red days makes the page reload and the user is scrolled to the top. Not nice UX. Instead should not scroll and the blob should simply switch once this is updated in the backend. Also, the list of "undantag" should auto-update because this is a react frontend which can update only the parts that need to do so when the data updates. The data should become stale since we do an action (flip between working and non-working) and then it should auto-refetch and thus update the UI.
 
@@ -19,6 +20,8 @@ PL days, so should the vacation days be possible to change
 is super annoying. (And an issue we have already talked about). The way to do it is with a debounce and autosave
 WITHOUT reloading the entire page.
 
+- I don't understand the vacation calculations right now, it doesn't give me confidence: For Jacob it says that he has 30 days, 15 are planned so thus 15 are left. Then it says that only 10 are saved for next year (which is correct since I can only save what is over 20), but it says that 0 are expiring! This is super important to warn/highlight, so that Jacob takes out more vacation. And maybe that the planner should make sure to say that we should switch out PLs (if possible) to vacation to not expire any days. This would lead to more PL days, which can lead to the ability to be on time off longer in the future. Image that shows how it currently looks like here: ![](./vacation_issues.png)
+
 ## medium prio
 - Update all deprecated things in the backend code.
 - check the "open" in todo.md, if they should be done

nextTodo.md

@@ -0,0 +1,19 @@
+- Check how the "Förskolans planeringsdagar per år" is used: Automatically just removed from the count?
+    - This should be a per year "how many did you take" so that we also know the true number each year
+    to better understand how many days might go lost.
+    - This also needs to be displayed better in the overview.
+
+- Clicking the Ledig/Arbetsdag in the list of all red days makes the page reload and the user is scrolled to the top. Not nice UX. Instead should not scroll and the blob should simply switch once this is updated in the backend. Also, the list of "undantag" should auto-update because this is a react frontend which can update only the parts that need to do so when the data updates. The data should become stale since we do an action (flip between working and non-working) and then it should auto-refetch and thus update the UI.
+
+- How does it work when the other parent wants to login? beacuse that parent should be connected to the same
+plan and same child. This whole user flow needs to be looked over.
+
+- Inputting the number of vacation days is now only possible for the logged in parent, but not possible
+to change the other parent (if available). This should be done since we are able to change the other parent's
+PL days, so should the vacation days be possible to change
+
+- Updating the amount of vacation days now leads to needing to click save for each year in the settings, that 
+is super annoying. (And an issue we have already talked about). The way to do it is with a debounce and autosave
+WITHOUT reloading the entire page.
+
+- I don't understand the vacation calculations right now, it doesn't give me confidence: For Jacob it says that he has 30 days, 15 are planned so thus 15 are left. Then it says that only 10 are saved for next year (which is correct since I can only save what is over 20), but it says that 0 are expiring! This is super important to warn/highlight, so that Jacob takes out more vacation. And maybe that the planner should make sure to say that we should switch out PLs (if possible) to vacation to not expire any days. This would lead to more PL days, which can lead to the ability to be on time off longer in the future. Image that shows how it currently looks like here: ![](./vacation_issues.png)