-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update Cadence Tutorials 1-6 to be more interactive and streamlined #172
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Great work!
I mostly reviewed the changes in the language reference
They are working for me in preview. It's possible one or two are broken or missing? I'll do a pass to check before merging |
Co-authored-by: Joshua Hannan <[email protected]>
Co-authored-by: Joshua Hannan <[email protected]>
Co-authored-by: Joshua Hannan <[email protected]>
Co-authored-by: Joshua Hannan <[email protected]>
docs/tutorial/06-fungible-tokens.md
Outdated
|
||
Execute `Get Balances` again. | ||
Every Flow account is initialized with a default Flow Token Vault in order to pay for storage fees and transaction [fees]. If an address is use, it will be able to accept fees, without a user or developer needing to take further action. If that account becomes lost, any tokens inside will be lost as well. |
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.
they could delete it in a transaction, but after the transaction finishes executing, it would revert because it won't be able to provide any fees for the transaction or a minimum balance to cover storage fees, so it would never actually work.
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.
Thanks for addressing everything! I'm okay with you merging once you've addressed the last few comments. And I trust that you've also updated the code in the links to include the changes to the code since the last time I reviewed. I did not verify and test them myself in the playground again this time
Co-authored-by: Joshua Hannan <[email protected]>
Co-authored-by: Joshua Hannan <[email protected]>
Co-authored-by: Joshua Hannan <[email protected]>
No description provided.