Support for truffle@5
See original GitHub issueLately there have been some issues with latest versions of tools from the truffle suite.
Some update to the typings should happen sooner or later, or else TypeChain will become obsolete.
My first contact with Solidity ecosystem was just a few weeks ago and only with the most current versions, so I’ve managed to create a project that’s cross-compatible internally.
With a little bit of work I might have something that could serve as an update to the truffle-typings, but that’s also still compatible with TypeChain and existing example projects.
Would anyone be interested in that?
I already have something that works, I just need some guidance in what is actually needed.
Here is a link to my fork of the project: cymerrad/truffle-typings
Issues I’m facing currently are, for example:
- What would be the preffered way of interacting with the package? Right now, in the example project mentioned eariler, types are being provided by tsconfig.json options:
{ "typeRoots": ["./node_modules/@types", "./types"], "types": ["node", "truffle-contracts"] }
This requires specifing all the types needed for the project, not just the truffle’s.
IMHO, the dream-scenario would be just by importing@types/truffle-contract
(otherwise the TS server will not know where to find the declarations outside of the typeRoots specified). However, could we still make it compatible with TypeChain? - Should I provide all the properties existing on the objects and how deep should I go? From my experience with the truffle-contract project, I’d have to suggest a lot of changes to their project, as their usage of getters/setters is just pure insane.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:14 (6 by maintainers)
Top GitHub Comments
Issue Status: 1. Open 2. Cancelled
The funding of 200.0 DAI (200.0 USD @ $1.0/DAI) attached to this issue has been cancelled by the bounty submitter
I know it has been over half a year since starting this issue, but I just had too much on my plate, and then I had to take a long hiatus from everything.
The issue is non-existent anymore - everything works well out-of-the-box, just as intended.