Retired
E.T needs to call() home again! (retired)
Loading description...
Fundamentals
Objects
Data Types
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.
This comment has been hidden.
Hey Johan, I'm sorry you found this kata confusing but thanks for seeing it through and giving me some feedback. I'll pull this Kata later on tonight as I need to spend a little time removing the unnecessary over-complications. Thanks again.
needs random test cases :)
Is this supposed to be a puzzle?
(Puzzle != Good kata)
No it shouldn’t of been. Two things I wanted to test for were the use of call method and accessing objects dynamically. Added extras to be removed.
Ok. It can be hard to write a good kata.
My suggestion is to write the most basic possible verison of the functionality you're trying to demonstrate, try and eliminate anything that isn't directly related (A lot of people like to add in unnecessary input validation requirements - avoid this.) then after that think about adding a story.
Description needs to be a little bit clearer on what is supposed to be happening.
Needs more test cases.
If you've got two functions that need to be implemented you should make sure both are fully tested.
Cheers for the feedback Insti, I’m going to change it over the weekend. I think adding ET’s algorithm and possibly an ascii code to access the nested object has bloated the description and made the task confusing. I only want (1) use of the call method (2) accessing object dynamically. If you wouldn’t mind having a look when complete, be much appreciated.