Time to split up this project? about swashbuckle.aspnetcore.filters HOT 5 CLOSED

Well, I don't really want to take on the maintenance burden of having n number of other NuGet packages to manage. I also have the older sister Swashbuckle.Examples project to look after, and most changes to this package needs to be ported to that one and vice versa.

Granted, there's not much code here to maintain but I don't have a lot of spare time.

I get what you mean - this package has basically become a dumping ground for stuff I've found handy while using Swashbuckle for the last 3 years or so. If I was going to make any changes, then maybe it should be renamed to something like Swashbuckle.AspNetCore.Contrib. But I'm not sure renaming a NuGet package is a good idea, it would likely cause problems for those already using it. Maybe? I don't know.

I also think it would be a bit silly to have a NuGet package containing only a single class of about 20 lines.

from swashbuckle.aspnetcore.filters.

What about one project for Examples and one other project for "everything else", that being a contrib project?
Agreed having a bunch of projects with a handful of lines in them is likely overkill.
You could put out a call for volunteers to help maintain the repos?

from swashbuckle.aspnetcore.filters.

I thinkt the examples should be part of Swashbuckle Core, but the project itself is just not moving at all, so problems like this project are inevitable.

from swashbuckle.aspnetcore.filters.

Since the project has been added to and is no longer just Swashbuckle.AspNetCore.Examples, I have decided on a new name Swashbuckle.AspNetCore.Filters. I've already renamed the repository, I will carry on and rename the files in the src folder

from swashbuckle.aspnetcore.filters.

Rename complete, I think the new name makes more sense. Released https://www.nuget.org/packages/Swashbuckle.AspNetCore.Filters/

from swashbuckle.aspnetcore.filters.