5 kyu
Config Parsing: INI
Loading description...
Parsing
Algorithms
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.
needs a bump to newer Node versions
Approved
Objects are not JSON. You're asking for a plainObject(well, possibly nested, but basically plain). Please amend the Description.ALso, did you really think you'd get away with not having random tests? :P
Apart from that, nice kata!
Resolved; rephrased description and implemented a random config generator
Nice job.
There's still a reference to JSON somewhere, and I'd use
Test.assertDeepEqualsinstead ofTest.assertSimilar(Objects don't really have an order of their properties - you can't fully rely on insertion order), but those aren't showstoppers.Updated accordingly Thx for the feedback