-
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
[RFE] Explain tables in Aptos #5517
Comments
how to deserialize table from raw bytes to rust struct with bcs,any sample for reference? |
Thanks to Daniel, we also have: |
I have started a glossary entry for Table here: And I am linking to @banool 's excellent Stack Overflow answer here: I would love to publish these instructions, still not in site navigation: Team, please advise. Thanks! |
We have removed the Stack Overflow link. Please take another look: |
We are live! Closing this out as all I could muster here. If someone else wants to contribute, I'd love that. |
Reopening to see if we can get more details in the docs. |
What is about the reference docs generated from the source? |
This? We link from: Yet I don't know if that addresses this particular request. Perhaps we should also reference table use from our guides to demonstrate use. Wolfgang, what do you think? Thanks! |
This issue is stale because it has been open 45 days with no activity. Remove the |
The docgen from the code doesn't have enough explanation. |
This issue is stale because it has been open 45 days with no activity. Remove the |
Still not fixed. This should be stale-exempt. |
RFE
Tables are a common area of confusion in Aptos. We should explain them, building upon a definition proposed in:
#5434
See the sources we have now:
https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-stdlib/sources/table.move
https://aptos.dev/guides/move-guides/guide-move-transactional-testing/#view-tables
https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-stdlib/doc/table.md#0x1_table
Note, the second link isn't in navigation. We should fix that too. Asking @banool and @movekevin for guidance and help.
The text was updated successfully, but these errors were encountered: