Thanks for your interest in improving JetTreeMark-vscode! Your feedback, bug reports, and code contributions make this extension better for everyone. 🚀
-
Report Bugs
If you encounter an issue, please open an issue under JetTreeMark-vscode Issues with clear steps to reproduce, your OS, and VS Code version. -
Suggest Enhancements
Have an idea for a new feature or improvement? Open a feature request in Issues, and we’ll discuss the best approach. -
Pull Requests
- Fork the repository.
- Create a branch from
main:git checkout -b feature/your-feature-name
- Implement your changes.
- Add or update tests if applicable.
- Commit with a clear, descriptive message.
- Push to your fork and open a PR against
main.
-
Follow the existing TypeScript conventions:
- Use ESLint and Prettier (run
pnpm run lint). - Keep code modular, with small, focused functions.
- Document public APIs and React components as needed.
- Use ESLint and Prettier (run
-
VS Code extension best practices:
- Use the
vscodenamespace for API calls. - Avoid synchronous file I/O on the UI thread when possible.
- Keep the Webview UI in
webview-ui/isolated; treat it like a separate frontend project.
- Use the
-
Clone & install
git clone https://github.com/HichemTab-tech/JetTreeMark-vscode.git cd JetTreeMark-vscode pnpm install -
Build the Webview UI
cd webview-ui npm install npm run build cd ..
-
Compile the extension
pnpm run compile
-
Launch in development
- Open in VS Code:
code . - Press F5 to run the Extension Development Host and try out your changes.
- Open in VS Code:
-
Package a
.vsixpnpm run package # or: vsce package
Your contributions help everyone share and document their project structures more easily. Happy coding!