Docs to explain why behind breaking changes

Open
#2,426 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, openapi
Domain
documentation

Research direction

Start by reading the existing upgrade guide, which covers what changed and how to upgrade. Identify the OpenAPI.NET 2.0 breaking changes it lists, then add companion documentation explaining the rationale behind them; done means customers can understand why the changes were made.

Written by the indexing model from the issue text.

Description

type:documentation

Customer request:
The OpenAPI.NET 2.0 GA will bring a lot of breaking changes and customers need to understand the "why" behind them.

Ask:
Author documentation to explain the why. We currently have an upgrade guide which show the "what" and "how" to upgrade.

Dominant language
C#
Stars
1.6k
Forks
286
Avg merge
6h 38m
Merged PRs (30d)
35

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/OpenAPI.NET

All issues in microsoft/OpenAPI.NET

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.