Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Changing default case of schema properties

未关闭
#118 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
typescript
领域
tooling

调研方向

Start with config.ts and the ConfigBase type, then trace how generateSchemaTypes and generateFetchers consume schema properties and required names. Decide whether casing belongs in configuration or a generation step, and define the expected behavior for both property and required names. The issue is done when the chosen behavior is implemented consistently and its scope is agreed.

由索引模型根据 Issue 内容生成。

描述

Hi,

I have a question about changing the case of generated schema properties.

Our OpenApi specification is generated from .NET API. Since all exported object properties have pascal case by default, generated schemas have also pascal, which is not TS/JS convention. It can be solved by these suggestions.

  • Changing the case in config.ts file. This method is not ideal, but works.
		to: async (context) => {
			const filenamePrefix = 'api';
			const { openAPIDocument: { components } } = context;
			for (const schema of Object.values(components?.schemas || {})) {
				if (!isSchemaObject(schema)) {
					continue;
				}
				const { properties, required } = schema;
				if (properties == null) {
					continue;
				}
				for (const propertyName of Object.keys(properties)) {
					const stored = properties[propertyName];
					delete properties[propertyName]
					properties[_.camelCase(propertyName)] = stored;
				}

				if (required != null) {
					for (let i = 0; i < required.length; i++) {
						const propertyName = required[i];
						required[i] = _.camelCase(propertyName);
					}
				}
			}
			const { schemasFiles } = await generateSchemaTypes(context, {
				filenamePrefix,
			});
			await generateFetchers(context, {
				filenamePrefix,
				schemasFiles,
			});
		},
  • Adding a new config parameter to override casings. It may look like the example below. I can make a PR for that if necessary.
export type ConfigBase = {
...
    filenameCase?: keyof Pick<typeof c, "snake" | "camel" | "kebab" | "pascal">;
  casing?: {
    schema?: {
      property?: keyof Pick<typeof c, "snake" | "camel" | "kebab" | "pascal">;
    }
  }
};

Which option is better? If none, how should solve this issue?

Thx for your answers.

主要语言
TypeScript
星标
634
派生
83
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fabien0102/openapi-codegen 的其他 Issue

查看 fabien0102/openapi-codegen 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。