AppExplorer

AppExplorer is a tool for creating detailed internal architecture diagrams that are linked to the code they represent. It is designed to help team leads and lead developers create accurate and easy-to-understand diagrams that simplify the complexity of their codebase while maintaining a stable and reliable connection to the underlying code.

AppExplorer integrates with VSCode, allowing developers to create cards linked to specific sections of code based on file paths and symbol names. These cards can also be used to navigate VSCode, making it easy to update the links as the codebase evolves.

When you open a card and its target symbol has been renamed, you'll land in the same file, but the card may become disconnected. However, AppExplorer provides an "Attach Card to Code" command that allows you to re-attach the card to the new symbol name or location, ensuring that the diagram remains accurate and up-to-date.

The cards created by AppExplorer link to GitHub, providing a stable anchor that can help developers quickly navigate to the code that needs to be changed. By maintaining this connection between the diagrams and the codebase, AppExplorer ensures that the documentation remains accurate and reliable, even as the codebase evolves.

If you're interested in contributing to the project, AppExplorer's Miro board provides an onboarding resource that allows you to explore the codebase and understand how it is structured. You can also suggest new features or improvements to the tool, or help maintain and update the existing documentation.

Features

AppExplorer: Create Card

• Identifies the symbol under the cursor
• Locates where it's defined and attaches a card to it

AppExplorer: Attach Card to Code

• Attaches the currently selected card to a symbol in the code

Requirements

This extension requires Miro and to enable the AppExplorer addon.

Download the latest app-explorer-*.vsix from https://github.com/dropbox/AppExplorer/tags. I'm not distributing it in the VSCode market because it's only useful with Miro, with that Miro added installed. I've already gone through the process to get it approved withing Dropbox

# This assumes you only have 1 version downloaded
code --install-extension app-explorer-*.vsix

Contributing

If you want to work directly on AppExplorer you need to globally install @vscode/vsce.

npm install -g @vscode/vsce

This extension operates by opening a webserver on http://localhost:50505/. This is the URL that the Miro extension will load in the background to connect with VSCode. The code in the /public folder is NOT configured to run through a transpiler, so it's JavaScript with TypeScript/DocBlock annotations. It's better than nothing, but it doesn't provide the safety of a real TypeScript file.

If you open the project and press F5 or run the command Debug: Start Debugging, it will launch a temporary VSCode running the extension. I don't think this process accounts for the /public folder though.

I'll usually just build and reinstall with this:

rm *.vsix; vsce pack && code --install-extension app-explorer-*.vsix

1. Rebuild and install
2. Refresh Miro
3. Refresh VSCode

If you don't refresh Miro, you can get a mix of old /public/miro.js code along with newer changes in src.

Known Issues

• The project is very incomplete at this stage

Release Notes

• 0.0.6 - Code Navigation

  • Selecting a single card in Miro will bring you to the code
  • Clicking App Explorer (# cards) on the status bar lets you QuickPick a card
    • Miro will move to show yoy the cards as you search
    • Choosing a card will select it in Miro
      • Selecting the card will also navigate to the code.
  • All cards on the board use Miro's native linking feature for permalinks.
  • If you have a card selected in miro, you can AppExplorer: Attach Card to Code to reattach it to a symbol you're looking at.

• 0.0.7 - AppCards

  • Up through version 0.0.6 I've been using Miro Cards that can be edited on the board. This makes it too easy to accidentally overwrite titles.
  • When selecting a card from an older version, it will be migrated to a new AppCard and then removed.
    • I couldn't get it to reliably place the new card over the old one, so it just puts it in the center of the viewport.
  • All new cards are AppCards

• 0.1.0 - Improved Navigation

  • This version uses Miro's normal app_card:open event (round button in the top-right corner of the card) to navigate. The previous version was navigating when you select a single card.
  • 

• Tag Selected Cards

  • Create or remove Miro tags on AppCards.