Cadence 1.0 (formerly known as "Stable Cadence")

[turbolent]

🚨 Testnet Upgrade blockers

Beta Give feedback

1. Release new Emulator with [Cadence 1.0 migration] Add EVM storage account creation migration flow-go#6422

Features

Beta Give feedback

No tasks being tracked yet.

Tech Debts / Chore

Beta Give feedback

1. Stop migration if --chain parameter does not match state #3335
   +0
   
2. Account Capabilities entitlement effectively entails all entitlements cadence-lang.org#166
   documentation +1
3. Warn developers in migration guide to check inferred entitlements are not more permissive than necessary #3268
   Documentation +1
   
4. Update checker/interpreter NFT tests to use actual NFT contracts #2503
   Technical Debt Testing +2
   
5. Re-enable disabled contract tests #2719
   Technical Debt Testing +2
   
6. Remove uses of and definitions for AuthAccount/PublicAccount types after migrations
7. Account export (https://www.notion.so/dapperlabs/Cadence-Implementation-Sync-Notes-Agenda-640389e72df942668d89deadd8d291de?pvs=4#c854ad5cc91b4a88922557449f5be3b9)
8. Revert changes in #2764 after Stable Cadence #2766
   Feedback Technical Debt +2
9. Replace Test.TestAccount with Account #2726
   Feature Feedback +2
10. Improve documentation: Improve Documentation in the leadup to Cadence 1.0 cadence-lang.org#26
11. https://www.notion.so/dapperlabs/Cadence-Implementation-Sync-Notes-Agenda-640389e72df942668d89deadd8d291de?pvs=4#72e9a6394ad44c3883f5d515772f95e3
12. Improve documentation: Full pass of language reference, follow up on e.g. tutorial
13. JSON-CDC needs to support TypeValue of AttachmentType #3108
    Feature Technical Debt +2
14. JSON-CDC needs to support decoding Attachment #3113
    Feature Technical Debt +2
15. Runtime needs to support importing Attachment and TypeValue of AttachmentType #3114
    Feature Technical Debt +2
16. https://github.com/dapperlabs/cadence-internal/issues/187
17. Update docs to explain state migration side-effects on accessing stored values #3206
    Documentation Feedback +2

Maybe? (on-hold)

Beta Give feedback

1. Need a way to force delete resources #2170
   Feature Feedback +2
2. Relax default entitlement mapping for dictionary/array elements #2953
   Feedback Improvement +2
3. https://github.com/dapperlabs/cadence-internal/pull/116

[turbolent]

@onflow/cadence I wonder if we maybe want to clear out all the done items in the list, to only leave what is left, so it is easier to see?

[SupunS]

I moved some on-hold items to a separate section Maybe?(on-hold), to make it more clear on the "must do" items.