swagger-api/swagger-codegen

All typescript client should have to possibility to generate packaging information

Open

#2,694 建立於 2016年4月24日

在 GitHub 查看
 (9 留言) (4 反應) (0 負責人)HTML (12,701 star) (5,474 fork)batch import
Client: TypeScriptEnhancement: Featurehelp wanted

描述

For now only the typescript-angluar2 client generates it's own packaging information. All Typescript clients should able to generate their own packaging information. Next information should be generated:

  • package.json
  • tsconfig.json
  • typings.json (optionaly)

I would suggest to only generate these files when the npmName option is passed.

貢獻者指南

技術棧
typescript
領域
toolingdeveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with swagger codegen template structureUnderstanding of TypeScript project setupKnowledge of npm package generation
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The angular2 client already generates package.json, tsconfig.json, and typings.json. You should locate the template files and generator code for the angular2 client in the repository (likely under modules/swagger codegen/src/main/resources/typescript angular2 and the related generator class). Then extend the same logic to all other TypeScript client generators (e.g., typescript angular, typescript node, typescript fetch) by checking the `npmName` option. Ensure the files are generated only when `npmName` is provided. Consult the existing implementation for reference and test with sample OpenAPI specs.
All typescript client should have to possibility to generate packaging information · swagger-api/swagger-codegen#2694 | Good First Issue