feat: adds utility service and access to commander

[jmcdo29]

There is a new CliUtilityService and @InjectCommnder() decoraotr
that allows for direct access to the commander instnace. The utility service
has methods like parseBoolean, parseInt, and parseFloat. The
number parsing methods are just simple wrappers around Number.parse*(),
but the boolean parsing method handles true being yes, y, 1,
true, and t and false being no, n, false, f, and 0.

[nx-cloud]

Nx Cloud Report

CI is running for commit 4d93adb.

📂 Click to track the progress, see the status, the terminal output, and the build insights.

---

Sent with 💌 from NxCloud.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4d93adb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[jmcdo29]

@micalevisk @smolinari would y'all mind taking a look at this and checking my logic along with what the addition is? Thanks guys

[micalevisk]

I'll try this feat out next saturday. The logic seems fine.

---

I think would be cool to add in-code docs like

/**
 * A helper method to turn a string (case insensitive) into a boolean based on true or false values.
 *
 * Any string that matches one of the following values is considered a `true` input:
 * - `yes`
 * - `y`
 * - `true`
 * - `t`
 * - `1`
 *
 * Any string that matches one of the following values is considered a `false` input:
 * - `no`
 * - `n`
 * - `false`
 * - `f`
 * - `0`
 *
 * @param val
 * @throws {Error} If `val` is not a _true_ nor _false_ expression
 */
parseBoolean(val: string): boolean {

and

/**
 * A Simple wrapper around `Number.parseInt()`
 * @param val
 * @param radix
 */
parseInt(val: string, radix = 10): number {

/**
 * A simple wrapper around `Number.parseFloat()`
 * @param val
 */
parseFloat(val: string): number {

to improve DX a bit. Although this is redundant as they're documented already on the docs site.

[jmcdo29]

I'll try this feat out next saturday. The logic seems fine.

I think would be cool to add in-code docs like

/**
 * A helper method to turn a string (case insensitive) into a boolean based on true or false values.
 *
 * Any string that matches one of the following values is considered a `true` input:
 * - `yes`
 * - `y`
 * - `true`
 * - `t`
 * - `1`
 *
 * Any string that matches one of the following values is considered a `false` input:
 * - `no`
 * - `n`
 * - `false`
 * - `f`
 * - `0`
 *
 * @param val
 * @throws {Error} If `val` is not a _true_ nor _false_ expression
 */
parseBoolean(val: string): boolean {

and

/**
 * A Simple wrapper around `Number.parseInt()`
 * @param val
 * @param radix
 */
parseInt(val: string, radix = 10): number {

/**
 * A simple wrapper around `Number.parseFloat()`
 * @param val
 */
parseFloat(val: string): number {

to improve DX a bit. Although this is redundant as they're documented already on the docs site.

Yeah, I think the doc string would definitely be helpful for in IDE docs. It's just that none of the other methods have that, so adding it might feel out of place.

[smolinari]

From what I can see, looks good. 👍 Asking me to check your work is like master Po asking Grasshopper if his Kung Fu is good. LOL! 😁

Scott

[micalevisk]

@jmcdo29 how do we import this new service?

it isn't listed below

[jmcdo29]

Whoops, missed that. See this is why I have someone double check me

[coler-j]

How do we use this?

[jmcdo29]

@coler-j Is there something not understood about the documentation?