feat(utils): add parseCommands utility to format custom command configs

[HamedHaghani]

Description

This PR adds a utility function parseCommands in src/utils/parseCommands.ts.

It takes a commands object (e.g., from a config file) and parses it into an array of command objects with name, key, and description properties. This sets up the project to better support custom command configurations.

Closes #553

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• I have read the CONTRIBUTING document.
• My commits follow the commitizen commit convention
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[jwu910]

Hi @HamedHaghani thanks so much for being interested in contributing to this project! It's definitely been a long time since we have had any time to try to improve and update it.

I skimmed over the PR and the issue associated, and I had a few questions. The PR doesn't quite seem complete as I only see one file add which includes an exported function. I was thinking maybe there was some implementation work that didn't get pushed up.

Do you have any extra information on how this is getting implemented into the current workflow of the application and/or how a user would take advantage of the feature?

Happy to try to help answer any questions, but please have some patience, too, as I may not be able to respond right away.

[HamedHaghani]

Hi @jwu910 – thanks for the kind reply and for reviewing my PR! You're right — the current PR only includes the `parseCommands` utility function, as the original issue (#553) focused on just creating the parsing logic. I didn’t integrate it into the app yet because there wasn’t an obvious place where command parsing was already being used in the current flow, and I didn’t want to add extra changes beyond what was asked. That said, I’d be very happy to help implement or connect it into the workflow — maybe reading from the config file or extending CLI behavior — if you can point me in the right direction! Thanks again for your time and support 😊 Sent from Yahoo Mail On Wednesday, May 28, 2025, 2:48 PM, Joshua Wu ***@***.***> wrote: jwu910 left a comment (jwu910/check-it-out#555) Hi @HamedHaghani thanks so much for being interested in contributing to this project! It's definitely been a long time since we have had any time to try to improve and update it. I skimmed over the PR and the issue associated, and I had a few questions. The PR doesn't quite seem complete as I only see one file add which includes an exported function. I was thinking maybe there was some implementation work that didn't get pushed up. Do you have any extra information on how this is getting implemented into the current workflow of the application and/or how a user would take advantage of the feature? Happy to try to help answer any questions, but please have some patience, too, as I may not be able to respond right away. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>