Add support for non-payable ink! constructors

[HCastano]

Right now the UI assumes that all ink! constructors need a value (renamed from endowment in paritytech/substrate#10082). However, with use-ink/ink#1065 this is no longer the case.

The UI should only display the value field in case the constructor is marked as payable. This behaviour is already implemented by the UI for ink! messages.

Reference of the screen where a value/endowment is asked for (Developer > Contracts > Upload and Deploy Code):

[jacogr]

Needs an ABI update (V3) where the flags are passed through on the constructors. Currently V2 of the ABI defines -

ContractConstructorSpecV2: {
    label: 'Text',
    selector: 'ContractSelector',
    args: 'Vec<ContractMessageParamSpecV2>',
    docs: 'Vec<Text>'
  },

(messages are slightly extended form the above with payable, mutating and identifier fields).

Marked as <substrate> since it needs a versioned update to the ABI formats. (Which si to be supported in the API)

[HCastano]

The metadata will be bumped with use-ink/ink#1100

[jacogr]

@HCastano Brilliant, thank you! Will make an issue linking though to that PR to get in support on the API layer.

[jacogr]

The value seems only passed-through when the constructor is payable, aka

apps/packages/page-contracts/src/Contracts/Deploy.tsx

Line 87 in c8a262b

value: contractAbi?.constructors[constructorIndex].isPayable ? value : undefined

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.