Validation for available commands. about cli

[Souvikns]

There is a bug, CLI is breaking in production, it runs fine but shows a warning, you can look into #192. We are migrating to a new version of oclif #203. Can you merge this branch and try once.

Let me know if this problem is resolved.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

yup, still needed, we use https://www.npmjs.com/package/levenshtein-edit-distance already in generator -> https://github.com/asyncapi/generator/blob/master/lib/templateConfigValidator.js#L67

it is pretty nifty and should not be difficult to add I think

[ron-debajyoti]

Hey, can I take this up?

[derberg]

@ron-debajyoti definitely 👍🏼

[ron-debajyoti]

Hi @Souvikns ,
I was exploring to fix the issue, but I can't really figure out where do I catch the mismatch of the commands.

For example :

• when I try to run asyncapi validate wrongCommand or a command where I use one of the supported commands but a wrong input parameter, then the catch function in src/base.ts catches it, but
• when I try to run asyncapi invalidCommand, I don't see the above catch function in src/base.ts catching it. I think oclif directly handles there isn't such a class defined under src/commands. How do I handle such cases?

Please correct me if I got something wrong.

[Souvikns]

Yeah, you are right if there isn't a class in the commands folder then oclif handles it. You can refer to this. Also, check this out for this issue, there are some premade plugins that would help us achieve this.

[ron-debajyoti]

Hey @Souvikns , sorry for not responding to this earlier.

I looked into the plugins and figured using @oclif/plugin-not-found would solve the problem. I tried installing it and also @oclif/plugin-help, but I'm getting plugin module errors during executing. Trying prepack also showed the import errors.

The error looks like this :

I suspect this might be due to @oclif/plugin-help dependent on @oclif/core and we are using @oclif/config, Seems like have to make our own plugins instead of using existing ones but I would like to have you take a look into it as well.

[ron-debajyoti]

Let me know if this problem is resolved.

Yep, it worked!

So since you're waiting for that PR to get merged, do I open a PR too for this issue?

[Souvikns]

Yeah @ron-debajyoti you can go ahead and open a PR.

[asyncapi-bot]

🎉 This issue has been resolved in version 0.16.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀