lol mannn now I feel real silly for my solution I ended up initializing state like... name: typeof this.props.name !== 'undefined' ? this.props.name : 'Yeti', to get that default prop test passing

doesn't work on hooks, had to use GPT chat for refactoring

UPD wrong tests! if I specify the default input state as 'Yeti' it throws an error :
Controlled Beast with empty beast name passed
should set the default name to empty
Expected: '', instead got: 'Yeti' <
OK, than I change to ""
And catch new error wtf:
Controlled Beast without props passed
should set the default name to Yeti
Expected: 'Yeti', instead got: ''

Muito confuso esse teste!

looks like this is outdated as it still uses classes

In this kata author used old method to create ref in react(https://stackoverflow.com/questions/43873511/deprecation-warning-using-this-refs). I passed tests only because I saw test preparations and used console.log.
Some problems you may have with global function unshakle.
Good luck and have fun

This function needs to call an already existing function unshackle with the beast to release.

It expects the name of the beast to release, not the beast itself.

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

It would be great if add label to this kata

<label htmlFor="controlledName">Beast name:</label>

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