100 Days of Code Day 58
Should you really be using Enumerable.Range() and other LINQ stuff when a simple FOR loop will do. No, no you should not. It is silly and makes your code harder to read. The only reason you would do that is to show off. That is exactly what community solutions were doing for today’s exercise Series. In that one you find all substrings of a given length within a string. Of course there were hidden expectations in the test cases that I check for substring length reasonableness and throw an argument exception if not good. Which may have been reasonable if they didn’t have this little gem in the description which implies it is the callers fault if they pass bad data.
“And if you ask for a 6-digit series from a 5-digit string, you deserve whatever you get.”
As for the Todo List I have been working on. Well, I broke it. I thought I would have to start over from scratch. I did some odd things when checking into Github which left the code stranded and deleted in the void.
I did manage to eventually piece it back together. Let that be a lesson don’t try funny stuff and commit to source control early and often.
I also:
- Hid the secrets as desired.
- It now runs against a PostgreSQL server
- Added tests for the complete route
That leaves:
- Pagination
- Handle unavailable name error on signup
- Redirect back to the todo list on add/edit
- local deployment (