FIX: Generate structs for constructor arguments

[aakoshh]

Motivation

I noticed that the Abigen did not generate a struct for the constructor parameters. This was a struct that did not appear anywhere else in the interface, so I thought it was because ethers only generates bindings for interacting with an already deployed contract, especially because there was an open issue seemingly asking for this feature: #1239 and also because the generated deploy method took a generic input parameter.

Upon closer inspection it looked like it should generate structs for the constructor inputs, however this did not happen because the constructor (at least in our case) didn't have a name. This would normally be the name of the function, but since a constructor doesn't need any, it's empty.

Solution

Use the name "constructor" if the item.name is empty.

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[mattsse]

cool, tysm