Question about ethers.getContract LESSON 10

[AlexK020908]

In lesson 10, as we are working on a deploy script that updates the front end :

const { ethers } = require("hardhat")

//write a script that is connected to the front end
module.exports = async function () {
    if (process.env.UPDATE_FRONT_END) {
        console.log("i[datomg front end")
        updateContractAddresses()
    }
}

async function updateContractAddresses() {
    const raffle = await ethers.getContract("Raffle")
}

for

await ethers.getContract("Raffle");

why did we not specify a deployer/signer parameter like we did in the tests?

 raffle = await ethers.getContract("Raffle", deployer)

does the second parameter mean that we deployed the contract with the wallet address "deployer" ?
I have tried researching about this and this explanation came up:
ethers . getContract ( contractAddressOrName , contractInterface ) Returns a new connection to a contract at contractAddressOrName with the contractInterface. Prototype

What does contractInterface mean? and when should we include that second parameter like we did in tests/when shouldn't we?

[alymurtazamemon]

@AlexK020908 If there is no signer available, getContractAt (updated old one getContract) returns read-only contracts.

Now, why were we using signer in tests? so the answer is that we wanted to change the state of the blockchain in tests (for understanding this click on the read-only above and read that.).

[iangechuki]

ethers.getContract("raffle") gets the deployed contract and connects it to deployer by default. ethers.getContract("raffle",deployer) does the same thing but explicitly defined who is connected .Here the deployer is the account address.I know am drifting away but bear with me.You can also say let raffleContract=await ethers.getContract('raffle').and then explicity connect it to the deployer like this.await raffleContract.connect("signer")..When you use this The signer is not equal to the deployer.You get the signer from ethers like this const accounts=await ethers.getSigners().To get deployer from array of signersdeployer=accounts[0].When using contract.connect() make sure you use signer not address.await getNamedAccounts() gives you the address of deployer not signer .Back to your question in tests you can get the contract like this ethers.getContract("raffle") and it will be connected by default to the contract.or explicitly state who is connected by adding deployer as second parameter on getContract() but it will depend on your use case. Like you will do when creating nft marketplace in a later lesson you will need to have one account list the nft and another buy the nft.In order to do this the contract will need to connect to different signers at different times .I think of it like this the signer passed to connect is person whose who just hit the connect button on the frontend and is currently connected to our smartcontract.If you still dont understand Patrick will explain in later section am sure you will get it.About the contract interface I havent use it with the hardhat-deploy package yet