### Describe the bug So there's 3 different bugs that I'm facing What I did is run the script and also `echo` out the command from the deploy script 1. No constructor Contract isn't deploying as it expects `--constructor-args` `forge create ./src/${Test}.sol:${Test} -i --rpc-url $rpc --constructor-args` 2. Constructor present 1 parameter This works perfectly `forge create ./src/${Test}.sol:${Test} -i --rpc-url $rpc --constructor-args 10` 3. Constructor present >1 parameters Only the first parameter gets passed `forge create ./src/${Test}.sol:${Test} -i --rpc-url $rpc --constructor-args 10` ### To Reproduce in the describe the bug ### Expected behavior Deployed contracts ### Additional context I think it could be due to `read -ra args` and adding a length check for args to differentiate error case 1 from 2 and 3
Describe the bug
So there's 3 different bugs that I'm facing
What I did is run the script and also
echoout the command from the deploy scriptNo constructor
Contract isn't deploying as it expects
--constructor-argsforge create ./src/${Test}.sol:${Test} -i --rpc-url $rpc --constructor-argsConstructor present 1 parameter
This works perfectly
forge create ./src/${Test}.sol:${Test} -i --rpc-url $rpc --constructor-args 10Constructor present >1 parameters
Only the first parameter gets passed
forge create ./src/${Test}.sol:${Test} -i --rpc-url $rpc --constructor-args 10To Reproduce
in the describe the bug
Expected behavior
Deployed contracts
Additional context
I think it could be due to
read -ra argsand adding a length check for args to differentiate error case 1 from 2 and 3