-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TS SDK] Initialize sdk_v2 folder structure and basic usage #9448
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I now realize this is mostly just copy pasta, so I'm going to stop commenting on it, but keep in mind anything that's been copied over, and had a bug that was fixed in it, will now diverge.
May just be better to write it from scratch with empty files, and just have all the license, and setup files etc.
add aptos config add aptos config support new client implement new client support and use post request create types folder add gitignore add utils folder add openapi generated types add types folder add transactions folder add crypto folder add bcs folder add api folder add account folder move files location export aptos api error class export files modify tests install openapi and modify build commands
@@ -0,0 +1,2 @@ | |||
// hardcoded for now, we would want to have it injected dynamically | |||
export const VERSION = "2.0.0"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder are alpha versions supported in npm?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ohh yea, we were thinking on publishing the new SDK under @aptos-labs
namespace to comply with all other packages aptos labs holds https://www.npmjs.com/settings/aptos-labs/packages , so something like @aptos-labs/sdk
we can think about it later down the road
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the plan to create a new sdk_v2 folder, then slowly migrating everything over to sdk_v2, and eventually deprecating/replacing the existing one?
the plan is to create a sdk_v2 that holds sdk v2 files. some would be ported over from v1 and new ones. eventually we would have 2 folders, sdk and sdk_v2 and just publish sdk_v2 under a new name. we keep the sdk folder b/c we need to keep maintaining it for some time |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
Description
This PR is the first step for the sdk_v2 development process. It includes only the basic structure, client files, Aptos class in
aptos.ts
and AptosConfig inaptos_config.ts
Test Plan