Feature Request: Add minimal-API-style routing as Extension Package #707

Closed
opened 2025-12-29 15:31:29 +01:00 by adam · 6 comments
Owner

Originally created by @GennadyGS on GitHub (Jul 28, 2025).

Originally assigned to: @StefH on GitHub.

Proposal: Add the routing features implemented in the WireMock.Net.Routing library (https://github.com/GennadyGS/WireMock.Net.Routing) to WireMock.Net as an extension package under the https://github.com/wiremock organization.

Details:

  • The WireMock.Net.Routing library provides minimal-API-style routing for WireMock.Net.
  • It provides extension methods for expressive, maintainable, and testable HTTP routing, inspired by ASP.NET Core Minimal APIs.
  • It can serve as a reference implementation for the proposed extension package.
  • Integrating these features as an official extension will benefit users who need more flexible routing in their WireMock.Net setups.

Reference:

Please consider this feature request and evaluate the possibility of adding these routing features as an extension package.

Originally created by @GennadyGS on GitHub (Jul 28, 2025). Originally assigned to: @StefH on GitHub. Proposal: Add the routing features implemented in the WireMock.Net.Routing library (https://github.com/GennadyGS/WireMock.Net.Routing) to WireMock.Net as an extension package under the https://github.com/wiremock organization. Details: - The WireMock.Net.Routing library provides minimal-API-style routing for WireMock.Net. - It provides extension methods for expressive, maintainable, and testable HTTP routing, inspired by [ASP.NET Core Minimal APIs](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis?view=aspnetcore-9.0). - It can serve as a reference implementation for the proposed extension package. - Integrating these features as an official extension will benefit users who need more flexible routing in their WireMock.Net setups. Reference: - Example implementation: https://github.com/GennadyGS/WireMock.Net.Routing Please consider this feature request and evaluate the possibility of adding these routing features as an extension package.
adam added the feature label 2025-12-29 15:31:29 +01:00
adam closed this issue 2025-12-29 15:31:30 +01:00
Author
Owner

@StefH commented on GitHub (Aug 5, 2025):

@GennadyGS
Interesting idea!

I'm thinking if this needs to be a separate project or just be included is this solution...

@StefH commented on GitHub (Aug 5, 2025): @GennadyGS Interesting idea! I'm thinking if this needs to be a separate project or just be included is this solution...
Author
Owner

@GennadyGS commented on GitHub (Aug 5, 2025):

Thanks for response.

I think it would be better to add the extension directly into the main solution—either as a separate package or inside the main package. I'm totally fine with both options.

@GennadyGS commented on GitHub (Aug 5, 2025): Thanks for response. I think it would be better to add the extension directly into the main solution—either as a separate package or inside the main package. I'm totally fine with both options.
Author
Owner

@StefH commented on GitHub (Aug 9, 2025):

Best is inside this repo + solution.

Maybe as name WireMock.Net.Extensions.Routing because it's an extension to to main logic?

@StefH commented on GitHub (Aug 9, 2025): Best is inside this repo + solution. Maybe as name `WireMock.Net.Extensions.Routing` because it's an extension to to main logic?
Author
Owner

@GennadyGS commented on GitHub (Aug 9, 2025):

Agree

@GennadyGS commented on GitHub (Aug 9, 2025): Agree
Author
Owner

@GennadyGS commented on GitHub (Aug 9, 2025):

Is anything required from me?

@GennadyGS commented on GitHub (Aug 9, 2025): Is anything required from me?
Author
Owner

@StefH commented on GitHub (Aug 10, 2025):

You can create a PR which adds this src + test.

@StefH commented on GitHub (Aug 10, 2025): You can create a PR which adds this src + test.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/WireMock.Net-wiremock#707