swagger-api / swagger-api/swagger-codegen

Provide logger instead of sys outs.

Open
#2,205 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi,
During client code generation getting below sysouts. It would be great if you provide logger instead of sysouts.

Sysout:
reading from....
writing file

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

The issue names no file or test. Start by tracing client code generation and locating the “reading from....” and “writing file” messages, then identify the project’s logging entry point. Done means these messages are emitted through the logger instead of raw sysouts.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.