Fix kudo amount input.

[marcianosr]

What

Explain what changes inside the code, this can be as simple or complicated as you want as long as it's clear

Why

Explain why these things are changes. This explanation is for your colleagues and your future self.

Code Review

Please consider the following checklist when reviewing this Pull Request.
More background and details here.

• Does the code actually solve the problem it was meant to solve?
• Is the code covered by unit tests? Integration tests?
• Does anything here need documentation? (Focus on why, not what.)
• Does any of this code deal with privacy sensitive information or affects security? Ask an additional reviewer.
• Is the code easy to understand and change in the future?
• Is the same code or concept duplicated? Find a balance between DRYness and readability.
• Does the code reasonably adhere to the Kabisa coding standards?
• Be kind.

[codeclimate]

Code Climate has analyzed commit 7ab8e9f and detected 2 issues on this pull request.

Here's the issue category breakdown:

Category	Count
Duplication	2

The test coverage on the diff in this pull request is 0.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 12.8% (0.0% change).

View more on Code Climate.

[sandercamp]

Nice one! Made it work without resorting to hacky solutions I see.

Minor thing I noticed: when a value is selected and I want to change it again the cursor is positioned before the input value. Backspace will still empty the field though.

[sandercamp]

Removing the autofocus will reintroduce the issue where the input loses focus when changing the value using only the keyboard. The root cause is the fact that the whole component rerenders when the value is updated, I think. Enabling autofocus was/is an easy workaround, but there might be a better solution.

[marcianosr]

Should be picked up later in refactoring phase