IMO, if you think a piece of code doesn't have any value standing on its own, then it doesn't need to be a component (arguably).
Input could be a component when
You could style your input the way you need and reuse it throughout your code.
You compose your input with validation or any other functional need and expose it as a single reusable component.
Input need not be a component when You don't have the need to reuse it and will probably need it only once in your code (very unlikely scenario for input but you get the point).
I would suggest breaking down your code into as many components as possible because it will make your code look clean and readable but at the same time over componentizing everything is not recommended.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it all comes down to reusability.
IMO, if you think a piece of code doesn't have any value standing on its own, then it doesn't need to be a component (arguably).
Input could be a component when
Input need not be a component when
You don't have the need to reuse it and will probably need it only once in your code (very unlikely scenario for input but you get the point).
I would suggest breaking down your code into as many components as possible because it will make your code look clean and readable but at the same time over componentizing everything is not recommended.