Closed RawichK closed 2 years ago
We already parse contract names elsewhere, so it's fairly straightforward to enable something like
"signers": [
{
"account": "@owner",
"scopes": "CalledByEntry, CustomContracts",
"allowedcontracts": ["GasToken"]
}
]
Also, the Value is not accepted
warning can be safely ignored. The json schema for scopes property is wrong, but that doesn't affect the actual value parsing of the property by the debugger. But that should ALSO get fixed
labeled bug and feature. warning is a bug, specifying allowed contract by name is a feature. But they are both small enough there's no point in splitting them into separate issues.
Location: signers object in launch.json
The
scopes
can be specified as "CalledByEntry, CustomContracts" and works well but it shows a warningValue is not accepted. Valid values: "None", "CalledByEntry", "CustomContracts", "CustomGroups", "Global".(1)
The
allowedcontracts
accept only contract hash, but contract hash changes every time re-build / re-deploy, so#contractName
notation should be added (the same format as invoke files).