feat: cli should validate only yml, yaml and json extension files

[AayushSaini101]

Reason/Context

Please try answering a few of those questions

• Why do we need this improvement?

According to the latest version of the CLI, it will generate only yml, yaml and JSON file extensions, but the validate is still validating the files of different extensions like exe etc

[AyushNautiyalDeveloper]

hi I would like to work on this. @AayushSaini101 please assign this to me. and also project me to correct direction on where can i start to work on this.

[Souvikns]

@AyushNautiyalDeveloper, @AayushSaini101 opened the issue and might be working on it so you need to ask him if you want to work on this issue.

That being said some points I would like to share about the problem

asyncapi.ymal.yaml as per the example shared in the issue is still a valid name for a .yaml file so, in theory, this behavior is expected.

This is the function that loads and parses the spec file,

cli/src/commands/validate.ts

Line 27 in 4f2412a

const specFile = await load(filePath);

If you read the function you will notice that CLI loads the spec from three different ways, from

• filesystem
• URL
• Context

This is how we are reading the file from the filesystem, we don't really check what format of the file is as long as it is valid YAML or JSON.

cli/src/models/SpecificationFile.ts

Line 77 in 4f2412a

static async fromFile(filepath: string) {

Since we already have a check for file formats while running the new command makes sense to have it for validation as well. Also, I think we can create a new Error Type called Invalid AsyncAPI file type(Error name up for debate) since we have more than one scenario for the same error.

[AyushNautiyalDeveloper]

hi @AayushSaini101 can I work on this task or it is already worked on? please let me know.

[AayushSaini101]

@AyushNautiyalDeveloper Please take this issue #800