Improve Documentation in the leadup to Cadence 1.0

[bjartek]

Issue to be solved

Review cadence docs

Language Reference

Tasks

Preview Give feedback

1. https://cadence-lang.org/docs/1.0/language/interfaces#types-and-event-definitions still uses old type requirements
2. Add a note about equality of runtime entitlements sets and intersection types to https://cadence-lang.org/docs/1.0/language/run-time-types
3. Should https://cadence-lang.org/docs/1.0/anti-patterns#public-admin-resource-creation-functions-are-unsafe be updated to use entitelments intead?

Tutorial

Tasks

Preview Give feedback

1. https://cadence-lang.org/docs/1.0/tutorial/first-steps#what-is-cadence this section is duplicated from the first page, so if you read the docs from start to first it gets a bit repetitive
2. signers here are not linked https://cadence-lang.org/docs/1.0/tutorial/resources#overview
3. the image used here https://cadence-lang.org/docs/1.0/tutorial/hello-world is not for cadence 1.0
4. the playground linked here is pre 1.0 https://cadence-lang.org/docs/1.0/tutorial/resources#overview
5. formatting of this code block is off https://cadence-lang.org/docs/1.0/tutorial/resources#create-hello-transaction
6. here we are using entitlements without describing it first. the user have no idea what it is at this point https://cadence-lang.org/docs/1.0/tutorial/resources#create-hello-transaction
7. the code example here is not 1.0 https://cadence-lang.org/docs/1.0/tutorial/resources#create-hello-transaction, it uses AuthAccount
8. this place is the first time a script has been mentioned https://cadence-lang.org/docs/1.0/tutorial/capabilities#executing-scripts, it should be explained before. Also it does not state that a script does not need to be signed.
9. this mentioned AuthAccount https://cadence-lang.org/docs/1.0/tutorial/capabilities#executing-scripts at the bottom of the section
10. use uint64 and not int here? https://cadence-lang.org/docs/1.0/tutorial/non-fungible-tokens-2#storing-multiple-nfts-in-a-collection
11. the example here does not send in the account as an argument and that is not best practise, should we change that? https://cadence-lang.org/docs/1.0/tutorial/non-fungible-tokens-2#transferring-an-nft
12. uses AuthAccount https://cadence-lang.org/docs/1.0/tutorial/fungible-tokens#create-store-and-publish-capabilities-and-references-to-a-vault
13. uses AuthAccount https://cadence-lang.org/docs/1.0/tutorial/fungible-tokens#transfer-tokens-to-another-user in lots of places

The bigger picture

These things might be strange about flow to others but it is not mentioned

• transactions and scripts are programs
• they compose
• an account can have multiple contracts
• an account can have multiple keys
• a key can be in multiple accounts

[j1010001]

Thanks for the feedback @bjartek , starting work on this.

[turbolent]

@joshuahannan Could you/your team maybe have a look at the item "Should https://cadence-lang.org/docs/1.0/anti-patterns#public-admin-resource-creation-functions-are-unsafe be updated to use entitlements instead?" item above?

[joshuahannan]

I checked it out and since the resource doesn't have a public capability, it doesn't need entitlements, so I checked it off this list