Slight update to relative path generation guide

[diagramatics]

The README.md threw me off when trying to generate a module or component that is nested in another module. This update reflects the solution in #2136 (the StackOverflow solution).

I don't know if there are plans to rewrite the section here, but if there are just close this PR 😄

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[diagramatics]

I signed it!

[googlebot]

CLAs look good, thanks!

[Meligy]

Instead of deleting these, I suggest you just add your example as the first example.

[diagramatics]

It doesn't work though? If I cd into a subdirectory and generate a component it doesn't actually generate the component in it.

[Brocco]

But they do work, we have tests that verify generation within the folder structure. Because of this I agree with @Meligy that your docs should be in addition to the existing docs.

[diagramatics]

Hm did I just found a bug then? I've tried this feature numerous times but I couldn't actually do this myself. Here's the history of what I did on 1.0.0.

ng new test-cli
cd test-cli
cd src
ls
cd app
mkdir feature
cd feature
ng g component new-cmp

[diagramatics]

Anyways since it seems to be a possible bug to an intended feature I've changed the PR to add the example instead of replacing it.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}