Efficient Contract Management with Direct GitHub Imports

Importing from GitHub streamlines contract development and prevents cluttering files.

### Streamlining Contract Interfaces: Importing from GitHub and NPM
* 🛠 Now that we have the interface, we can begin calling functions and addresses, but a **multitude of interfaces can clutter our contracts and files**, making them **cumbersome to manage**.
* 📂 In the past, with SimpleStorage, we utilized imports effectively since **all the code was locally available**, but we lack local access to the **AggregatorV3 interface and price feed contracts**.
* 🔗 Instead of manually copying and pasting code into new files, we can **directly import contracts from external sources** like GitHub.
* 📜 The documentation shows how to import using the syntax: `import at chainlink/contracts/src/...`, which aligns with the **GitHub repository structure**.
* 📦 This method allows us to **import directly from GitHub or npm**, eliminating the need for **redundant code duplication** in our project.
* 💻 By pasting the import line in Remix, it recognizes the path as an **npm package**, which fetches the necessary code from the **Chainlink repository**.
* ⚙ This approach simplifies our workflow, as it is equivalent to **copying the entire interface into our contract**, enabling us to **compile and proceed seamlessly** with the AggregatorV3 interface.

so now that we actually have the interface we can start calling these functions and calling these addresses. However, having a ton of these interfaces is really going to clog up our contracts and clog up our files and be really gross to work with. Is there a better way

for us to do this? Well, when we worked with SimpleStorage, yes, there was. We just went ahead and used imports, right? But that's when we had all the code in our directory locally. We don't have all the code locally. We didn't create the AggregatorV3 interface. We

didn't create the price feed contracts. So can we do something like import SimpleStorage.sol, but with a contract outside of our project? Well, again, we could copy paste it to its own file and import AggregatorV3Interface.sol. And of course, we're going to use this named

import syntax because we're awesome developers. We could copy paste it like this and do exactly what we did before. We could create a new file called AggregatorV3Interface, paste the code in there, or we could actually import directly from GitHub. If we go back to

the documentation associated with using data feeds, we scroll down to using data feeds here. So scroll down, we see at the top they do this import like this: import at chainlink/contracts/src/blah blah blah. This import actually has the same setup as the path of what's in

the GitHub repository. So instead of us copy pasting from GitHub, we can actually import directly from GitHub or npm. So we can copy this line back in our Remix, we could paste it in like this. Remix is smart enough to know that this at chainlink/contracts is referring to the

what's known as an npm package at chainlink/contracts at chainlink/contracts is what's known as a package manager and it keeps different versions of combinations of code for us to download at chainlink/contracts is created directly from chainlink repository remix downloads all this code

from npm which is created from the GitHub so it essentially downloads it from the GitHub so us doing this import like this is the same as is just copy pasting the entire interface at the top of our contract now we have this aggregator V3 interface that we want to

work with we go ahead and compile and bada bing bada boom

Lesson 4 Part 9 | Importing from NPM & GitHub - Solidity & Foundry Full Course

Book a smart contract audit here 👇
https://www.cyfrin.io/


Cyfrin Audits

Challenge: Managing Multiple Interfaces in Smart Contracts

Having many interfaces clutters contracts and files.

SimpleStorage used local imports, but external contracts are not locally available.

Option: Copy-pasting the interface into a local file and importing it.

GitHub documentation shows how to import using a path similar to the repository structure.

Remix supports direct imports from npm packages, which are linked to GitHub repositories.

npm acts as a package manager, providing different code versions.

Importing directly from GitHub is equivalent to copy-pasting the interface.

After importing, the contract can be compiled.