-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat: adds a wip SDK structure #130
base: main
Are you sure you want to change the base?
Conversation
} | ||
|
||
export class AuctionHouse { | ||
private settings: AuctionHouseSettings; |
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'd call those args or config. It's not exactly settings that are stored in a file or something.
|
||
constructor(private connection: Connection) { } | ||
|
||
get AuctionHouse() { |
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.
Why does this have to live on the client instead of just being returned?
i.e. if I'm done with it the GC cannot collect it now because it's still referenced.
Incurring that memory overhead only makes sense if creating it is expensive (which I don't think it is given you're just calling a constructor).
|
||
} | ||
|
||
async execute_sale() { |
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.
can we use camel case?
Thought about this a bit more and we should consider making the main import * as msdk from '@metaplex-foundation/sdk'
const house = msdk.getAuctionHouse()
await house.doSomething() If we include snippets like these in the docs then people will get it I think and advanced users can still do |
No description provided.