summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOskar <[email protected]>2024-04-04 21:13:54 +0200
committerOskar <[email protected]>2024-04-04 21:13:54 +0200
commit81f43e3057c2fb533595c3e624d2c11813aff1c2 (patch)
tree01f54e341c13990895efcba39dfea2f57f173625
parent4021c78435ab6044ed78ef06e46bf075beb2a959 (diff)
TODO update
-rw-r--r--TODO4
-rw-r--r--test/testgrounds/newlinetest2
2 files changed, 3 insertions, 3 deletions
diff --git a/TODO b/TODO
index 70ec34a..1308115 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,6 @@
TODO list. This is mostly so i can plan more granularly and remember small stuff i was working on last time and what i should prioritise first.
This is not my overall big planning board. (1 highest prio, 10 lowest)
-1 - All L functionality is done. Now i will have to test it and and fix any issues that come up.
-1 - Start implementing N.
+1 - Implement N functionality.
+2 - All L functionality is done. Did some testing and made some fixes. I will keep this here for now in case i find anything more.
2 - Not really a TODO point but more of an observation and a realisation i have made. I could have just used regex to do the validation of my commands. How about that... Well im too far in (sunk cost fallacy or whatever its called).
diff --git a/test/testgrounds/newlinetest b/test/testgrounds/newlinetest
index da31879..766a493 100644
--- a/test/testgrounds/newlinetest
+++ b/test/testgrounds/newlinetest
@@ -1,4 +1,4 @@
-1uhhhh
+1
2
3
4