microsoft / microsoft/OpenAPI.NET.OData
Assess Impact of Microsoft.OpenApi.NET Support for OpenAPI 3.1
Open
Nobody has claimed this yet.
priority:p2
status:needs-discussion
- Dominant language
- C#
- Stars
- 240
- Forks
- 70
- Avg merge
- 7h 59m
- Merged PRs (30d)
- 13
Description
We need to discuss the downstream effects of the Microsoft.OpenApi.NET library support for OpenAPI 3.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Microsoft.OpenApi.NET's OpenAPI 3.1 support and this repository's OData CSDL-to-OpenAPI generation scope. Identify downstream effects and affected consumers, then document a clear decision about compatibility or required follow-up work; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, openapi
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100