Feature request: Highlight created folders on generate dry runs

[TimTCrouch]

Command

generate

Description

When using the cli to generate new components, service, etc., if you are typing out the full path from the root to where you want the files created rather than navigating to that folder (which to me seems fairly common) if you misspell any part of the path, the cli does not know about the misspelling and takes this as a new path of folders to be created. Creating the new folders is of course necessary since users will add new folders into the path to be created intentionally. But it can take a bit to clean up a misspelling higher closer to the root in deeply nested paths.

Describe the solution you'd like

What feels like a fairly simple solution to this would be to lightly highlight any path segments that are going to be creating a new folder. This way the user can see if the folders being created match what they expect.

Describe alternatives you've considered

Currently the workaround is to type very slowly and carefully check every letter on deeply nested paths or navigate around the full structure of the application and run the command at the closest point to where the files will be generated.

[angular-robot[bot]]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.

[angular-robot[bot]]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot[bot]]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.