You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2022. It is now read-only.
Don't know, how best to tackle this? Should this also break with taking different types as input for generic encode and decode functionality, like also mirrored in the TypeScript interface PR #25? Or do a breaking release with separate encodeString(),... methods? Just allow Buffer values?
I think for starters (once #25 is merged) we can rewrite the project to produce that API. Once that's in place we can start updating the types. How do we feel about that?
You don't have to wait for #25 to be merged, this is not very much code and @ukstv was not responsive on this lately (mostly due to our fault since this took ages to go forward this so I wouldn't blame if he lost patience). But in doubt get in short contact on this, I am no TypeScript expert, so I also have separately the question if these separate definition files are still necessary if one is rewriting the whole library?
I am otherwise ok with the procedure, to keep the API on first iteration - if this keeps things easier - and then change on that later on.
Part of ethereumjs/organization#28
The text was updated successfully, but these errors were encountered: