-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to provide core package without content / scripts #128
Comments
This is a lot of work ... lately I rarely make any big changes to this project |
Looking at the contents of the package: |
Hey there! BR |
@markusbaumgartltdmsystems I really don't want to publish another package |
The Content and Tools are tiny files ... you can read more about that code: You could add an additional condition there to skip the move if it detects the other file/structure you are using |
That is what I actually do not want and submitted this request. |
In that case it will be best to modify the init.ps1 to skip the move when it detects your structure |
Would be best if you followed the standard ... but adding an exception in that PowerShell script is very simple, send a PR for that and I will review |
We are using swagger-net for some of our ASP.NET Framework projects within our company and where very happy to find an "up-to-date" alternative to Swashbuckle!
Actually we have a request to provide similar division of released NuGet packages:
We are used to add / configure swagger within another file/structure
rather than "SwaggerConfig.cs".
Many thanks in advance if that would be possible!
Note: For internal purpose I re-arranged the contents of the original package like shown in attached screenshot. (Although I did not put license etc)
The text was updated successfully, but these errors were encountered: