I wonder what are the future plans and features of Watermelon? Currently it feels like it does not bring a lot, or any, new things to VS Code ecosystem.
- GitLens is the extension every Git user should have installed, and it for example automatically gives you the git blame on every line
Then depending a bit on the version control system & language used, there are "native" extension for PR and documentation.
- Github pull requests & issues integrates nicely with the GitLens blame - hover the blame and you'll see the PR. Also has bunch of PR & Issues related functionalities
- autoDocstring (Python) for generating documentation "automatically" inside the code, where it belongs IMHO.
Hi and Ty for your comment. This is exactly the kinds of questions that we wanna see here because we learn new things with such.
1. GitLens is useful but it only gives you the author of a line, and the commit message. We can do way better than that as we keep indexing info from more sources + organize it in different ways
2. Similar as number 1. We will index info from more sources and organize it better.
3. Didn’t know about autoDocstring but it looks like a great analogous tool to JSDoc. We’ve used JS Doc and think it’s great for documenting functions. However, we believe there is an opportunity for documenting greater level stuff such as the architecture and the relations between modules.
- GitLens is the extension every Git user should have installed, and it for example automatically gives you the git blame on every line
Then depending a bit on the version control system & language used, there are "native" extension for PR and documentation.
- Github pull requests & issues integrates nicely with the GitLens blame - hover the blame and you'll see the PR. Also has bunch of PR & Issues related functionalities
- autoDocstring (Python) for generating documentation "automatically" inside the code, where it belongs IMHO.