You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current default Saunter configuration it generates errors based on the rule rule-path-lower-case-id in case when path contain {id}.
But this route template is very popular, it is used a lot in ASP.NET documentation: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-9.0
Maybe it is a good idea to exclude such paths from the rule?
The text was updated successfully, but these errors were encountered:
Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.
Please describe the feature.
With the current default Saunter configuration it generates errors based on the rule rule-path-lower-case-id in case when path contain {id}.
But this route template is very popular, it is used a lot in ASP.NET documentation: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-9.0
Maybe it is a good idea to exclude such paths from the rule?
The text was updated successfully, but these errors were encountered: