Move “open in editor” extension to core workflow

Created by: ryankscott

Useful links:

• Figma
• Old repo
• Doc

Tasks:

• Figure out settings structure
• Assemble supported IDE list
• Create branch
• Create URL getter
• Create action items container for the migrated extensions (git-extras, open-in-editor + view on the code host) – Copy styles from “ActionsContainer”
• Create a component for “open in editor” action
• Add settings to user settings
• Collect icons for the different supported IDEs
• Make the icon change to the IDE icon once settings are set correctly
• Create a custom useIde hook exposing an openInIDE callback
• Create a popover based on Sara’s designs
  • Dropdown clues: We don’t currently have a base dropdown component, but SearchContextDropdown (used to select a context from the search page) and DashboardSelect (used to find dashboards from the Code Insights page) should give an example of how to start putting this together. They use slightly different technologies under the hood (SearchContextDropdown uses reactstrap, and DashboardSelect uses reach) but we don’t have this standardized at all, use whichever option from those best suits our needs.
• Hook up popover to open
• Make sure keyboard navigation/interaction support is great! Our accessibility audit is upcoming!
• Create docs page to explain how to change settings
• Unit test build-url.ts
• Implement editor and base path saving in settings
• Migrate previous settings
• Add deprecation notices to the four repos

Test:

• Test it with all supported IDEs
• Test it on Windows with IntelliJ
• Test it with GoLand or some other JetBrains IDE that’s not IntelliJ
• Test it with an older IntelliJ version