microsoft / microsoft/OpenAPI.NET
Update SharpYaml dependency to v3.x
还没有人认领这个 Issue。
- 主要语言
- C#
- 星标
- 1.6k
- 派生
- 286
- 平均合并
- 6 小时 38 分钟
- 30 天内合并 PR
- 35
描述
Is your feature request related to a problem? Please describe.
OpenAPI.NET currently depends on SharpYaml v2. In my project, I use OpenAPI.NET to process OpenAPI documents and also need to read additional YAML-based configuration files.
SharpYaml v3 is a major redesign that introduces breaking changes compared to v2. Since OpenAPI.NET brings SharpYaml v2 as a dependency, I am currently forced to continue developing against the older SharpYaml API and plan a future migration.
Describe the solution you'd like
I would like OpenAPI.NET to update its SharpYaml dependency from v2 to the latest v3 release.
Describe alternatives you've considered
- Continuing to use SharpYaml v2 in my own code and migrating later.
- Isolating YAML processing behind an abstraction layer to minimize the impact of a future migration.
- Using a different YAML library for application-specific configuration files.
While these approaches are possible, they add complexity that could be avoided if OpenAPI.NET adopted SharpYaml v3 directly.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
定位项目中对 SharpYaml v2 的依赖声明,并在评估受影响的 OpenAPI YAML 处理之前,检查 SharpYaml v3 的 breaking changes。更新依赖后运行现有测试套件;完成的标准是使用 SharpYaml v3,并且 OpenAPI 文档的 YAML 处理仍保持兼容。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, yaml
- 领域
- api
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100