feat(core): support nested projects when deriving the project name from a given path #13349
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.
Current Behavior
The
getProjectNameFromDirPath
utility to derive a project name from a given path doesn't support a workspace with a project at the root and/or nested projects. This causes things like the Tailwind CSS utility to get the glob patterns for a project's dependencies (used by the Angular and React plugins) to fail and not return any glob pattern.Expected Behavior
The
getProjectNameFromDirPath
utility to derive a project name from a given path supports a workspace with a project at the root and/or nested projects.Related Issue(s)
Fixes #