RegisterCommands method

[tkow]

Close #705.

I also add two sections named with Command Runner and Regsitere Commands to your docs and fix links broken I found in 4a3dd2d.

apps/docs/pages/commander.md

apps/docs/pages/api.md

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit dfdf7cd. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 2 targets

• nx e2e integration --skip-nx-cache
• nx affected:build --parallel

---

Sent with 💌 from NxCloud.

[changeset-bot]

🦋 Changeset detected

Latest commit: dfdf7cd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
nest-commander	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[tkow]

@jmcdo29
Please, close it if you don't like it as I describing in #705.

[jmcdo29]

Could we call this registerWithSubCommands? That way the intent is clear. The code is actually really clean, and if the command is clear enough then I don't see why we can't add it in. Thanks for adding the tests too, showing it works is really nice.

The only other thing I would ask is can you update the documentation? Just a new section in the Commander section would do

[jmcdo29]

Oh, also, would you mind running pnpm changeset and following the wizard to create a minor changeset for the nest-commander package? That will help automate the release of this once I merge it in.

[jmcdo29]

A couple of grammatical revisions. Thanks for all the work!

[jmcdo29]

If everything (save for the sending coverage) passes, this PR will be great! Thanks again.

[tkow]

@jmcdo29

Thank you for reviews, in fact, I'm not native English speaker, so I apologize for many grammatical mistakes.

I have no idea to fix CI / send-coverage, so could I ask you how to fix it?
I may not allowed to run the github action's step (https://githubhelp.com/codacy/codacy-coverage-reporter-action/issues/33).

BTW, I really think this library is awesome and I have been making many our command line tools standalone and want it more known widely especially in my country, Japan. It can be used not for nest application but for command line tools builder. If you don't mind it, could you let me translate docs in ja locale when I have time?
And, sorry for that I make you work even though today is Xmas. I'll give you my gratitude from sponsored page though it may be little for you. Have a nice day.

[jmcdo29]

I have no idea to fix CI / send-coverage, so could I ask you how to fix it?

It's just because of a missing API token for Codacy. Don't worry about it :)

[jmcdo29]

If you don't mind it, could you let me translate docs in ja locale when I have time?

Go for it! So long as you don't mind helping maintain them as well when changes happen 😄 I use AstroDocs for the documentation, which has multiple language support already built in.

[tkow]

@jmcdo29

It's just because of a missing API token for Codacy. Don't worry about it :)

So, Is there nothing I should change in this PR?

If everything (save for the sending coverage) passes, this PR will be great! Thanks again.

Sorry for I'm not familiar to nx e2e test, but do I still have something to have to add extra configuration to do this?

Go for it! So long as you don't mind helping maintain them as well when changes happen 😄 I use AstroDocs for the documentation, which has multiple language support already built in.

Thanks! I'll try it.

[jmcdo29]

So, Is there nothing I should change in this PR?

Nah, it's all good