RicoSuter/NSwag

Why not have the NSwag studio as an extension to VS

Open

#548 opened on Jan 30, 2017

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)C# (1,357 forks)batch import
help wantedproject: NSwagStudiotype: enhancement

Repository metrics

Stars
 (7,359 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

It should be a lot easier if it's part of Visual Studio as a VSIX. The entire generation process could be automated easily. It could be integrated with the project/solution settings in Visual Studio. Defaults configuration can be set right from VS' options.

Contributor guide

Research direction
Examine the existing NSwag codebase to understand the code generation logic. Research how to create a Visual Studio extension (VSIX) that integrates with the .NET project system. Propose a high level design for embedding NSwag Studio as a VSIX tool window.
Tech stack
csharp
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Visual Studio ExtensibilityC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40