Allow users to change metadata when instantiating from hash

[statictype]

Right now when instantiating from hash or re-instantiating we pre-fill the file input with the stored metadata associated with the hash.

Would be nice to allow users to add a different metadata file. Similar to how the update metadata case is handled, we could display an x that removes the contents of the file input.

Note: the metadata here will be associated with the new contract instance. the code "bundle" stays associated with metadata it was first instantiated with.

[CharliePops]

Hey @statictype , I've playing around with the UI and I agree that this would be a nice UX improvement. I can address this issue though I have one question.

What would be the expected behavior if the user removes the file(click the x button)? shoud we revert the metadata information to the previous state(the original code hash) or just remove completely any metadata and force the user to select a new file or hash?

I can make a pull request for this, let me know.

[CharliePops]

I created a pull request using the 'revert' behavior since it what it makes more sense to me, but if that's not the expected behavior I can change it 😉 .

[statictype]

just removing it completely is perfectly fine. 👍🏻

[CharliePops]

No problem, I'll update the PR.

[statictype]

@CharliePops I think I misunderstood, the behaviour in the PR is what we want. no need for changes

[CharliePops]

Awesome 👍🏼