swagger-api/swagger-codegen

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

Open

#5,840 建立於 2017年6月13日

在 GitHub 查看
 (2 留言) (1 反應) (0 負責人)HTML (12,701 star) (5,474 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.
[Python] improving "packageName" and "projectName" in CLI options · swagger-api/swagger-codegen#5840 | Good First Issue