fix: vector arguments

[statictype]

fixes #431

For case 2 we display a new input which accepts a hex representation of Bytes.
I figure this is a bit better UX than working with decimal digits.

can you please test @xermicus?

[netlify]

✅ Deploy Preview for contracts-ui ready!

Name	Link
🔨 Latest commit	f871c7e
🔍 Latest deploy log	https://app.netlify.com/sites/contracts-ui/deploys/641dbb6616b6710007460b61
😎 Deploy Preview	https://deploy-preview-451--contracts-ui.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[xermicus]

This fixes the problem for me, thanks!

I also really like the new UX for bytes, way more convenient for larger byte arrays. However, I have a nitpick. The bytes input can be an odd number of hex digits. Considering an input of 0xBBB, it's not clear whether this will resolve to 0xBBB0 or 0x0BBB which are not the same. I suggest to only allow an even number of bytes (or 0).

[statictype]

0xBBB resolves to 0xBBB0

ideally we would have validation for these dynamic argument inputs but at the moment it's not possible. it needs a large refactoring.
i added a message below the input when the length is odd which clarifies the behaviour, but it doesn't prevent submitting the form.