swagger-api/swagger-codegen

[Python] improving "packageName" and "projectName" in CLI options

Open

#5,840 opened on 2017年6月13日

GitHub で見る
 (2 comments) (1 reaction) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Client: PythonGeneral: Suggestionhelp wanted

説明

Description

Here is the suggestion by @frol

Semantically, projectName should be the "most important" configuration, which would be used to generate packageName (meaning that it is the other way around than it is implemented now), BUT given the fact that packageName was introduced earlier, it makes sense to have this backward packageName to projectName generation. Can both projectName -> packageName and packageName -> projectName autogenerations be implemented? Does this make sense to you?

Swagger-codegen version

Latest master

Related issues

https://github.com/swagger-api/swagger-codegen/pull/5836``

Suggest a Fix

If anyone has feedback or wants to work on this enhancement, please reply to let us know.

コントリビューターガイド

技術スタック
pythonshell
領域
clideveloper experience
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Python basicsswagger codegen CLI usage
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
Review the suggestion in PR #5836 to understand the desired bidirectional generation between packageName and projectName. Examine the current CLI option handling in the Python module of swagger codegen, likely in the 'modules/swagger codegen/src/main/java/io/swagger/codegen/DefaultGenerator.java' or the Python specific generator. Implement the logic to allow both directions of autogeneration while maintaining backward compatibility. Test with existing configurations to ensure no breaking changes.