7 kyu
All Star Code Challenge #17
295 of 310shaddyjr
Loading description...
Fundamentals
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Series of duplicates / sub-overlapping problems Yes, most of them are retired, but now we need another manual labor / thread to retire this one too...
Needs update to current Node version.
For that, tests need to nest
assert
s init
s, notdescribe
s.Edited the kata (since the author appears to be absent from this platform), and it should be fixed now.
It's not mentioned whether the year 2050 is inclusive or exclusive bound.
It's both, because the correct answer can't even be 2050.
Closing.
Horribly undertested.
Not any more.
Don't know why this dude never fixed anything.
Seems like returning 0 for can't find year is really for input out of bounds. It feels artificial and insincere.
Just ask for input validation.