-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for nested gradle projects #88
Conversation
I want to do explore the possibility of not making the task name noisy, but instead utilizing task descriptions. That way the explorer won't be noisy with redundant information, and it will be clear which task belongs to which project in the command pallet. |
I can't add task details, this seems to be an internal thing (the npm extension sets task.detail but it's of type vscode.Task2 which is not exposed). |
31738de
to
8fbb788
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
483b68a
to
7565023
Compare
Refs #86
This adds support for detecting gradle projects in nested subdirectories. I might make this configurable...
Screenshots
Here is the latest changes with nested gradle projects grouped by relative folder name. This is done to prevent conflict with sub-projects which are displayed at the workspace root.
Example of deeply nested projects:
Here is the flutter project, grouped by "android" directory name:
Here is a gradle project without nested root project directories but with subprojects:
Here is the final UI showing how the tasks are labelled in the command pallet:
TODO