Tracking issue: 8/21 - 9/4

[beyang]

Discussion

Commands UI

This is not in a good state, we need to get it into a good state ASAP

• Command palette: all commands show up, so both /fix and /document should be present at the top level.
  • The "Submit a refactor" and "Submit question" options that appear if you start typing something else are inconsistent. These should correspond to a /command and indicate which.
  • We shouldn't group commands by whether they lead to a comment, the sidebar, or something else
  • Some basic intent mapping. If we can't do this fast enough beforehand, there should be some sort of confirmation afterwards.
• Sidebar REPL: all commands show up
• Inline REPL: I think we should eliminate this as a starting point for interactions (because we don't have an autosuggest capability in the text input here). We would still show this in case we need to show an inline response to the user, or maybe if the user wants to refine a /fix request.

Commands

• Search across symbols
• Test - Make it a smooth UI for accepting the generated test
• Fix - needs very smooth UI for viewing and accepting/rejecting the change, or refining the instructions
  • Consolidate /fix, /document, "refactor" into single /edit command?
• Document - Smooth UI for easily accepting generated docs

Tasks

Beta Give feedback

1. Search: indexed search improvements
2. Re-enable web build https://github.com/sourcegraph/cody/pull/770 #772
   clients/web-app +1
   
3. Autocomplete: Prepare for StarCoder evaluation experiment #760
   4 of 4
   autocomplete +1
   
4. Autocomplete: Expose rate limiting and other errors to users #634
   autocomplete clients/vscode design-ready +3
   
5. Autocomplete: Code navigation context #630
   autocomplete +1
   
6. Add info to autocomplete analytics events about embeddings availability. #754
   Stale autocomplete +2
7. Tree-sitter: Rank autocomplete suggestions based on syntactic validation #809
   autocomplete +1
   
8. Clean Up Quickpick & Keyboard Shortcut Interactions #631
   clients/vscode design-ready +2
   
9. Improve Generate Unit Tests #619
   clients/vscode enhancement +2
   
10. Improve Explain Code #618
    Stale clients/vscode enhancement +3
    
11. Fixup: Improve instruction flow #588
    Stale clients/vscode enhancement +3
12. Fixup: Move non-stop task list to a QuickPick #587
    Stale clients/vscode enhancement +3
13. Fixup: Use expanding ranges #585
    clients/vscode enhancement +2
14. Fixup: default inline chat behavior to fixup? #800
    Stale clients/vscode +2
    
15. "Code Smell" → "Find Code Smells" (or "Detect Code Smells")
16. Remove nesting commands from fixup/Refactor menu #765
    clients/vscode +1
    
17. Tree-sitter: Integrate tree-sitter into completions post-processing pipeline #849
    autocomplete +1
    
18. Tree-sitter: enable incremental parsing for tree-sitter #850
    autocomplete +1
    
19. Tree-sitter: streamline the post-processing logic #860
    autocomplete +1
    
20. Tree-sitter: truncate multiline completions based on parse-trees #910
    autocomplete +1
    

Needs discussion

Beta Give feedback

1. App-Less Onboarding Experience #632
   5 of 5
   clients/vscode design growth +3
   

   

Revisit next sprint

Beta Give feedback

1. Make it obvious in-editor when Cody has provided an autocomplete #667
   autocomplete clients/vscode dec-ga/vscode dec-ga: car design-ready +5
   
2. .codyignore file
3. Name suggestions feature
4. Codelens CTAs
5. Handling for questions that Cody can't answer #789
   Stale feature-request +2
6. Metrics for measuring impact of embeddings context on Loveability: https://docs.google.com/document/d/1UcjUdon1XO5GoLDIJJCGBq1zyhR6VfL2FE_apSPeLQo/edit#heading=h.wjyo6hfkbp25
7. Ask Cody: poor UX and formatting #867
   Stale clients/vscode +2