Migrate over to using `thenewboston-js` repo
Opened this issue ยท 13 comments
Make the AccountManager rely on thenewboston-js
repo fully
please get permission from me to work on it before you start
i don't believe the sdk library is ready yet. talk to @zinoadidi about the progress
This would be useful for this task.
https://docs.google.com/document/d/1FaPq2stWP0lMtHATNIfLA6ryMd0PtUYdcnrvZbUk7FI/edit
Its a documentation of the similar functions and their locations between Account manager and thenewboston-js
Hey @angle943, is the list of functions in the document above okay for the account manager or is there anything u would like to add to this list.
@tomijaga to be honest I currently don't have the bandwidth to look over the document in detail. But we can start going as is. Are you working in tandem with @zinoadidi about these issues?
@zinoadidi hmm perhaps it might be better to sync up offline later, but question for you, how soon do you think you can incorporate the AccountManager with the SDK? The reason why I ask is that we are soon having a switch to beta, which might end up changing a lot of our BE end points and results
@angle943 I have also considered this as well and the proposal is we are going to sync up the SDK development with beta updates as they come; I am working to secure one or two contributors who will be dedicated to this activity.
Concerning Account Manager, there is approximately 1 task pending test from the list of missing functionalities we started to work on a couple of days ago.
That means we can already start switching usage by Friday / weekend (@tomijaga is dedicated to this task)
According to our roadmap; we plan to keep the account manager in sync with SDK no matter what :) and we are ensuring this happens by such kinds of tasks thenewboston-blockchain/thenewboston-js#88
sounds good, here is the migration branch: https://github.com/thenewboston-developers/Account-Manager/tree/javascript-sdk-migration
Is this closed or bounty open ?