Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
This Kata is completely incorrect. If you think React then you can't solve it.
exactly what i did lmaooo
Appears to use React 15. So when I tried a hooks implementation, it failed.
Consider upgrading to React 17
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
It would be great if add label to this kata
It is hard to understand task.
I recieve an error :
"should have a form with the id beastForm
TypeError: Cannot set property 'value' of undefined"
I do have form with id beastForm.
To be fair, it's not really a bad practice. It's just not necessarily as performant. In a case like this it shouldn't really matter
Not a good practice to pass an anonymous function.
I think this kata's test cases are incomplete.
For my submitted (incorrect) solution, I've actually just submitted the beast value input by the test case in the beginning. The form input element's value is not used.
In a practical world where humans are inputing the form, I would have to read the form input value, then submit and run the requested function using that value.
The test cases did not use the
input
element to input value, hence I found my "wrong" solution accepted just using the test-case-injected value.Also, please update to >= React v16.4.x
There is
React.createRef
already. Kinda confusing when following the current (v16.11.x) documentation, but theReact.createRef
returns error upon testing.Definetely. Without it kata is useless
I didn't think the instructions were clear enough to be honest
Could you please update so we could use React.createRef?
I figured this out save for the fact that unshackle was an implicit global function. I erroneously concluded that the tests were missing a variable declaration.
I see now that it actually says "already existing function" in the instructions. I suppose that is clear enough, so I cannot complain. But maybe more explicitly writing something like:
"This function needs to call an already existing function unshackle in the global-scope with the beast to release."
Anyway, nice kata!
This comment is hidden because it contains spoiler information about the solution
Loading more items...