swagger-api / swagger-api/swagger-codegen

"Not Options For Commands" langs / versions in Brew-Installed Swagger Codegen CLI

Open
#10,109 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

The swagger-codegen CLI outputs the following two debug messages on each use:

12:10:37.020 [main] DEBUG io.swagger.codegen.v3.cli.SwaggerCodegen - there are not options for command 'langs'
12:10:37.021 [main] DEBUG io.swagger.codegen.v3.cli.SwaggerCodegen - there are not options for command 'version'

The CLI tool was installed using brew install swagger-codegen.

Component Version
macOS 10.15.3
Homebrew 2.2.10
Java Version 8 Update 241
Swagger Codegen 3.0.18
Swagger-codegen version
3.0.18
Steps to reproduce
+ brew install swagger-codegen

...

+ swagger-codegen version

12:19:24.177 [main] DEBUG io.swagger.codegen.v3.cli.SwaggerCodegen - there are not options for command 'langs'
12:19:24.178 [main] DEBUG io.swagger.codegen.v3.cli.SwaggerCodegen - there are not options for command 'version'
3.0.18

+ swagger-codegen langs

12:20:48.574 [main] DEBUG io.swagger.codegen.v3.cli.SwaggerCodegen - there are not options for command 'langs'
12:20:48.575 [main] DEBUG io.swagger.codegen.v3.cli.SwaggerCodegen - there are not options for command 'version'
Available languages: [aspnetcore, csharp, csharp-dotnet2, go-server, dynamic-html, html, html2, java, jaxrs-cxf-client, jaxrs-cxf, inflector, jaxrs-cxf-cdi, jaxrs-spec, jaxrs-jersey, jaxrs-di, jaxrs-resteasy-eap, jaxrs-resteasy, micronaut, spring, nodejs-server, openapi, openapi-yaml, kotlin-client, kotlin-server, php, python, python-flask, scala, scala-akka-http-server, swift3, swift4, swift5, typescript-angular, javascript]
Related issues/PRs

Included in the following issue, but the focus of that issue is not with DEBUG messages:

https://github.com/swagger-api/swagger-codegen/issues/9171

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the Homebrew-installed Swagger Codegen CLI using the version and langs commands, then trace the CLI handling of those commands and the emitted DEBUG messages. Done means both commands retain their expected output without printing the misleading DEBUG messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.