Recursive project search #85
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yogsototh
force-pushed
the
recursive-project-search
branch
from
e0f2160
to
8243fb2
Compare
greglook
requested changes
Dec 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduce a
/**notation for:project-dirsto recursively search for sub projects.We have a very big monorepo.
Its size is so big now that we would like to support a hierarchy in those sub projects.
Instead of manually writing all sub directories, I would like to search recursively.
Typically we already have
:project-dirs ["lib/*" "services/*"]and we would like to split some services but not have a flat organisation so:project-dirs ["lib/*" "services/**"]. This way we could take a servicefoosplit the code in 10 sub projects under thefoodirectory (that will no longer be a project directory).