asyncapi
help command is not working
Describe the bug
asyncapi help is not recognized as a command. The functionality for the help is working with asyncapi --help but the recommendation says to use asyncapi help .
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Yeah, we used to have a help command and then we removed it and now only allow help with the --help flag. With the new update with oclif to have an extra help command we have to use a plugin, so by default, we should have only the --help flag.
https://oclif.io/docs/help_classes
@Souvikns so we should remove the suggestion of help ? or add the plugin
I don't think we have any suggestions, for help, I am looking at the usage docs and I don't think we have anywhere specified about help command.
yeah, problem is I guess that we do not have control over the warning message that says asyncapi help
Ok so the warning is coming from a package that we use called @oclif/plugin-not-found where it creates a log message for help command https://github.com/oclif/plugin-not-found/blob/470096ba538e89fea043fa7a712404a450da6204/src/index.ts#L18 I don't think we can change that and it is misleading to the user to have a warning saying them to use asyncapi help command which does not exist so we have two options really
- create a help command
- it is actually a hook and we can write one for our use case and control the warning
what would be a good option?
IMHO
it is actually a hook and we can write one for our use case and control the warning
it is good to have only one command of help
if we are decided on going with the hook, can i please work on this ? @derberg @Souvikns
@kaushik-rishi I would also like to work on this ,have gone through oclif docs and cli structure
it is actually a hook and we can write one for our use case and control the warning
will we be hooking to the command_not_found event and then check if the command run was asyncapi help and then handle it ? If yes, how will we be handling it ?
@Souvikns
since @sambhavgupta0705 was first in the issue, he is allowed to take it first
@kaushik-rishi you can pick this one https://github.com/asyncapi/cli/issues/549 as it will also require digging into CLI and figuring how to provide meaningful error
@sambhavgupta0705 is.
Yes,I am working on it . We are waiting for @derberg approval
@fmvilas can you tell me how should i go about this. means i need to update on pluggin-not-found. of which i dont have direct control.
@sambhavgupta0705
We are waiting for @derberg approval
sorry but what approval?
@ayushnau did you have a chance to see https://github.com/asyncapi/cli/issues/559#issuecomment-1560578163 ?
@sambhavgupta0705
We are waiting for @derberg approval
sorry but what approval?
@ayushnau did you have a chance to see #559 (comment) ?
yes i started working on it.
https://github.com/asyncapi/cli/pull/843 @derberg also i came across this pr https://github.com/asyncapi/cli/pull/593 i would like to cover all the cases of command not found pluggin.
This issue has been automatically marked as stale because it has not had recent activity :sleeping:
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 :heart:
@prajjwalkapoor @Souvikns @derberg Should we considered this issue as solved by https://github.com/asyncapi/cli/pull/843 and then proceed to close it?
