Discovery of gaps in our dev journey

[j1010001]

time-boxed, Cadence devs dog-fooding the dev experience.

Brian's doc for the learning app: https://docs.google.com/document/d/1_c6fqqNYJnEZLcbhzkQ2nweXGrvkKtZLggCxjABY2Hc/edit?tab=t.0#heading=h.9yxznnjnjj8i

Tasks

Beta Give feedback

1. [LS] Update access modifiers to Cadence 1.0 cadence-tools#445
   Language Server bugfix +2
   
2. Improve test coverprofile flow-cli#1801
   Improvement +1
   
3. Fix counter script flow-cli#1802
   Bugfix +1
   
4. https://cadence-lang.org/docs/testing-framework still uses newEmulatorBlockchain
5. flow init generates IncrementCounter transaction which is not updated to Cadence 1.0 flow-cli#1815
   +0
6. [Test] Access to account (e.g. storage) only via transaction. Expose getAuthAccount cadence-tools#447
   +0
7. [Test] Test.readFile has Go stack trace when file does not exist cadence-tools#448
   Bug +1
8. [Test] State mismatch between test and blockchain cadence-tools#446
   +0
9. Add Cadence 1.0 Syntax Highlighting vscode-cadence#563
   +0
   
10. VSCode plugin installation via CLI doesn’t work flow-cli#1816
    Bug +1
11. Browsing projects show error flow-playground#816
    Bug +1
12. Get a list of all cases of an enum #3671
    Feature Good First Issue +2

[bluesign]

I can add one thing I still cannot manage to find the correct way to do :

var a : String?? = "deniz" // one or more optional 
var b: String? = .... ( get from a to b ) 

[turbolent]

@bluesign This issue is meant for the Cadence team to use Cadence and the Flow tools to build something, to experience them as developers do, and find gaps and bugs along the way. If you have a problem, please open a separate issue, thanks!