By using the deterministic function of deployments with a proxy in the form of an object with a specified proxyContract, the proxyArgs part doesn’t seem to work. Indeed, the default arguments is a 3 elements array ["{implementation}", "{admin}", "{data}"] that do not appear to be modified in the source code by passing a specific proxyArgs array argument. Despite the indication of an empty array, the error indicating 3 arguments persists (Error: expected 2 constructor arguments, got 3).
On the other hand, I don’t understand why I have to give two arguments for the constructor there as an UUPS proxy, knowing that I don’t have to specify these parameters for the deploy function or for the dedicated hardhat function:
Bug description
By using the
deterministic
function ofdeployments
with aproxy
in the form of an object with a specifiedproxyContract
, theproxyArgs
part doesn’t seem to work. Indeed, the default arguments is a 3 elements array["{implementation}", "{admin}", "{data}"]
that do not appear to be modified in the source code by passing a specificproxyArgs
array argument. Despite the indication of an empty array, the error indicating 3 arguments persists (Error: expected 2 constructor arguments, got 3
).On the other hand, I don’t understand why I have to give two arguments for the constructor there as an
UUPS
proxy, knowing that I don’t have to specify these parameters for thedeploy
function or for the dedicated hardhat function:To Reproduce
Error:
Expected behavior
In this case, I would give
proxyArgs: []
like in thedeploy
function case that works for this caseVersions