Struggling with project build logic....

[toddabraham]

Hi @PatrickAlphaC ,

I'm not sure if my discussion label is accurate, but let's see.

I'm on Lesson 13, and found myself facing the same error when trying to run deploy.py as I faced in Lesson 11 (#129 (comment)).

To me this highlights a hole in my understanding of what components need to be in place when building a project.

What areas should I be going back and reviewing to help fill this cognitive void in my learning?

All the folders listed above were copied from Lesson 13 Github repo, which concerns me as I feel I should have a better understanding of why we setup these mock contracts in a test folder inside contracts.

I'm rambling now, but I hope you understand my meaning here. Just trying to solidify my learning.

[cromewar]

Remember every time you add a new contract you should compile the whole project again, this allow brownie to add the contract into the build folder and access to it, could you please paste here a screenshot of your build folder?

[toddabraham]

Thanks @cromewar.

Here's my build folder:

[cromewar]

Actually i want to see this one build

did you try deleting it and compile again?

[toddabraham]

Here you go.

But at the moment I have no problems after creating all the test.sol files...

[cromewar]

Did the deploy script work fine?

Regarding to the highlights: this is because of the VSCode extension, for example let's suppose your compiler version is 0.8.0, and you import a test contract which uses 0.6.6 version, in most of the cases the version will come with this ^ symbol like this:

pragma solidity ^0.6.6;

Meaning that you can use any further version of solidity, and the compiler knows it. However the Vscode extension doesn't, if you use any other version the extension is going to complain about it... you can ignore this for now though. Hopefully the extension will get better with time.