Restructure and Refactor the file structure and code

[mbcse]

Description

As our project advances towards the integration of additional chains and functionalities, it becomes imperative to enhance the organization of our codebase for improved maintainability and clarity. The proposed solution involves a thorough refactor of the current folder structure, specifically segregating functionalities into distinct folders.

Objective

To establish a more organized and scalable folder structure that accommodates the growing complexity of integrating various chains and functions seamlessly.

Proposed Changes

Introduce a refined folder structure that categorizes functionalities based on their respective chains. Specifically, create separate folders for each chain, where the related contracts and associated functions will reside.

Example

project-root/
|-- chain1/
|   |-- contracts/
|   |-- functions/
|-- chain2/
|   |-- contracts/
|   |-- functions/
|-- shared/
|   |-- common/
|   |-- utilities/
|-- other_folders_and_files...

[AnmolSirola]

@mbcse I am participating in this year's GSoC and would like to contribute to the NFT-Toolbox project. May I take on this issue?

[mbcse]

Hey @AnmolSirola Yes Sure, Just work on the issue, No need to ask for approval:)

[AnmolSirola]

@mbcse I have come across two ways of refactoring the file structure.

Current state:

Note: I have used only Ethereum, Solana and Tezos for example. The same format will be used for Aptos and Flow.

refined structure 1:

refined structure 2:

Can you tell me which one of them would be better and suggest any changes. I will make a pr according to it :)

[mbcse]

Hey @AnmolSirola I think Structure 2 will be good.
Also Please move discussions to this repo now https://github.com/c2siorg/NFT-Toolbox.

[AnmolSirola]

@mbcse Sure :)