A feature can span backend logic, database queries and UI templates. I've been building Group Code, a VS Code extension that brings those related sections into a functionality tree. The relationships are explicit comments, such as @group Checkout > Payments. Add that group name to related sections in different files, then browse the group and jump to the source from the sidebar. The files keep their existing structure. One UI decision in the latest release was to remove the extra file-type level from the tree. A feature now shows its source entries directly. The attached walkthrough shows the workflow in a small checkout example. The trade-off is maintenance: the annotations need to stay useful as the code changes. They describe feature relationships, not inferred dependencies. I'd appreciate feedback on that trade-off. Would you maintain a few annotations for features that span multiple languages, or would this become another thing to keep in sync? What would make this useful in an existing codebase? I built and maintain the extension. Source and documentation: https://github.com/thechandanbhagat/group-code The walkthrough is also available here: https://youtu.be/DfgPVLwPMK4   submitted by   /u/thechandanbhagat [link]   [comments]