Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
blockiosaurus
left a comment
There was a problem hiding this comment.
Hey, this is great work! Looks like you have the process down and the instructions look solid.
One design pattern I don't think we've documented well enough is that we're trying to avoid overly-specific instructions at the moment. I think a more generic approach might be a V2 of UpdatePlugin that takes in an additional, optional buffer account and copies the data from there instead of from the arguments.
ed474f6 to
e99a8e8
Compare
27d6083 to
dc6fad2
Compare
Branch updated, tested by passing both plugin args in the usual way, and also the buffer account. |
…into update_attributes
Currently users have to deserialise their asset, get the attributes plugin, add an entry and then send that off in the update plugin instruction.
Adds an extend attributes function that just requires the new/existing pair to update which reduces the code users have to write and extends the number of attributes that can be included as you not longer hit the instruction size limit when performing CPI.