Repository navigation
RouteCheck 0.1.0
dotnet tool update --global RouteCheck --version 0.1.0Enhancements
- The routes are sorted by path, and routes with the same path by method (GET, POST, PUT, PATCH, DELETE, ...).
- New
-m|--methodoption to show only routes with the given HTTP methods, e.g.-m get,post. - New
-f|--filteroption to show only routes whose path contains the given text, or matches a wildcard pattern (*or%), e.g.-f "/pets*". - New
--outputoption (table,jsonormarkdown). Withjsonandmarkdown, only the result is printed, as one document, so RouteCheck works well in scripts, CI jobs and with LLM agents. Errors are part of the document. - Shows "No routes found." instead of an empty table.
- The web app is now built before it is started, and build errors are shown. The startup timeout no longer includes the build.
- New
--timeoutoption for the seconds to wait for the web app to start (default 20). --pathcan now also be a project file. RouteCheck looks for a*.csprojfile instead ofProgram.cs, so projects with their entry point in another file work too. If a directory contains several project files, RouteCheck lists them.- The web app is started in the
Developmentenvironment, so the OpenAPI endpoint is available without a launch profile. A launch profile orASPNETCORE_ENVIRONMENTstill takes precedence. - Clear error messages when the OpenAPI endpoint is missing (with a hint about
AddOpenApi()andMapOpenApi()), fails or returns no OpenAPI document. - The option
--openApiEndpointis now called--openapi-endpoint. The old name still works. - When the web app exits before it is ready, the error now shows its last output lines, e.g. the exception it crashed with.
- Ctrl+C cancels the check and stops the started web app.
- GitHub releases now take their notes from this changelog.
Bug fixes
- The started web app is now stopped reliably. Before, only the
dotnet runprocess was killed, so the web app itself kept running, also after errors. - The web app's output is now read continuously, so a web app that logs a lot no longer blocks during startup.
- The exit code is now
0on success and1on errors. Before, a successful check returned1and errors-1. - RouteCheck no longer fails when offline or when nuget.org is unreachable. The update check is skipped after at most 3 seconds.
- The update check now finds the latest version regardless of the order the feed returns them in.
- The update check now knows the installed version. Before, released packages reported
1.0.0internally, so no update was ever shown. - Paths containing
[or]no longer crash RouteCheck.
Commits: v0.0.3...v0.1.0