* Add SVG icons for map pins
* Add federation basis and new coordinator form (#793)
* Add new coordinator entry issue form
* Add Federation basis
* Fix eslint errors from F2F and fix languages
* Redo eslint @typescript-eslint/strict-boolean-expressions
* Robot Page working
* Contexts Working
* Garage Working
* CurrentOrder working
* Federation model working
---------
Co-authored-by: Reckless_Satoshi <reckless.satoshi@protonmail.com>
Co-authored-by: Reckless_Satoshi <90936742+Reckless-Satoshi@users.noreply.github.com>
Fixing the type handlePremiumChange function to handle the discount to the right type (React.ChangeEventHandler<HTMLInputElement | HTMLTextAreaElement>)
Using the correct type of handlePremiumChange function, then deconstructing the "value" var from the event.target
Using Number(value) in declaration of "newPremium", instead of using multiplication with number and string
To not affect another methods using "premium" var, I used isNaN func to make a check and set the initial value of "premium" var to zero (if is NaN) or newPremium (when valid number is entered)
The fix in the bug is the line "premium: isNaN(newPremium) || value === '' ? '' : premium," in setMaker. That makes the "premium" var to be set to zero when the input is empty or not a number, allowing the user to input the "-" (minus sign) and not entering 0 as before.
