Lesson 13: getLendingPool(account) in aaveBorrow.js

[ManuWeb3]

Hi all,

Is account a standard data type in JavaScript ?

If not, then how come it got declared in the function signature in getLendingPool(account) without any error ?

Is it because of the fact that JS is not type-strict ?

I know it got used to pass deployer as an address-type argument while calling this function, just wondering about its data type as I've just basic know-how of JS.

[krakxn]

The code in context please, along w/ the declaration for account

[krakxn]

Look:

async function getLendingPool (account) {

account is a parameter, we do not have to "declare" a parameter. We just have to specify a parameter for when we have to use the function.

A sample function:

let a, b

function sum (a, b) {
    // returns the addition result of a and b
}

function test {
    let testOne = 2, testTwo = 6, testResult
    testResult = sum(testOne, testTwo)
    return testResult
}

[ManuWeb3]

Thanks for explaining.

Precisely, my question is:
In solidity, we have to declare the variable type of parameters in the function definition, like (uint256 index) below:

function getPlayers(uint256 index) public view returns(address) {  
        return s_players[index];
    }

But, in JS, we don't do that as it's not type-strict. Right?

Below we did not declare the types of a and b in (a, b)

function sum (a, b) {
    // returns the addition result of a and b
}

[krakxn]

It is because JavaScript follows call-by-value (put simply, it does not get to know about the locations of the variables but just the value). Furthermore, as it is not a statically-typed—i.e. dynamically-typed—it requires the user to create conditionals, read documentation, or see the source code to ascertain the type of the parameters.

When you work on larger projects, the closest solution would be TypeScript as it will be much easier to debug.

[ManuWeb3]

Thanks for explaining the JS concept further.

A quick question as you mentioned TypeScript:
After completing Patrick's course, I planned to learn JS full blown but, lately, I've been coming across viewpoints of some senior developers in Web3 wherein they advise to rather learn TypeScript, not JS, as new protocols are adopting TS.

But, JS is still pretty much in fashion.

So, in your opinion (and I know it's bit off-track), Is it better to directly learn TS (and leave JS) ?
Or one has to learn both as both of these have their own significance in Web3 ?

Just your personal opinion... as I'm new to this space and learning lots at the same time gets overwhelming.

[krakxn]

TypeScript is literally derived from JavaScript, so there will not be any issues in transitioning to it. It will rather be easier (after a few days of playing around w the syntax), as TypeScript is more explicit in its declarations and less confusing than JavaScript.

However, using TS for small-scale projects is essentially meaningless. As it is not so hard to debug code there. So, it is primarily used in large codebases.