Closed arboleya closed 1 month ago
Basic sketch of what could be a starting point for the file structure.
abi
├── coder
│ ├── AbiCoder.ts
│ ├── encodings
│ │ ├── v1
│ │ │ ├── array.ts
│ │ │ └── enum.ts
│ │ └── v2
│ │ ├── array.ts
│ │ └── enum.ts
│ └── types
├── gen
│ ├── AbiGen.ts
│ ├── formatters
│ │ ├── configurables.ts
│ │ ├── enums.ts
│ │ ├── functions.ts
│ │ └── ...
│ ├── renders
│ │ ├── renderContract.ts
│ │ └── ...
│ ├── templates
│ │ ├── typescript
│ │ │ ├── contract-factory.hbs
│ │ │ ├── contract.hbs
│ │ │ └── ...
│ │ └── javascript
│ └── types
├── parser
│ ├── AbiParser.ts
│ ├── specs
│ │ ├── v1
│ │ │ ├── interface.ts
│ │ │ └── transpiler.ts
│ │ └── v2
│ └── types
└── test
├── fixtures
│ └── forc-projects
└── integration
We have addressed the key issues of this PR, so I am closing this as complete.
Instead of merely combining both packages in a single folder, the aim is to refactor them using the same structural approach. After recently modified Spec and Encoding strategies, and with future-proofing in mind, we can look ahead and strategize a proper foundation that should be resilient to future needs.
abi
package, basic infra for tests, etc.abi-coder/exhaustive-examples
test and tofuel-gauge/abi-contract
abi-typegen/*
tests and merge into the relatedfuel-gauge/abi-*
Sway program.abi-coder/encoding/**Coder
related tests into Sway