shelf_router

• Require analyzer: '>=7.4.0 <9.0.0'
• Require build: ^3.0.0
• Require build_config: ^1.1.0
• Require source_gen: ^3.0.0
• Require sdk: ^3.7.0

• Support the latest package:analyzer and package:source_gen
• Require sdk: ^3.3.0

• params is deprecated in favor of Request.params adding using an extension on Request.
• The default notFoundHandler now returns a sentinel routeNotFound response object which causes 404 with the message 'Route not found'.
• Minor breaking: Handlers and sub-routers that return the sentinel routeNotFound response object will be ignored and pattern matching will continue on additional routes/handlers.

Changing the router to continue pattern matching additional routes if a matched handler or nested router returns the sentinel routeNotFound response object is technically a breaking change. However, it only affects scenarios where the request matches a mounted sub-router, but does not match any route on this sub-router. In this case, shelf_router version 1.0.0 would immediately respond 404, without attempting to match further routes. With this release, the behavior changes to matching additional routes until one returns a custom 404 response object, or all routes have been matched.

This behavior is more in line with how shelf_router version 0.7.x worked, and since many affected users consider the behavior from 1.0.0 a defect, we decided to remedy the situation.

• Migrate package to null-safety
• Since handlers are not allowed to return null in shelf 1.0.0, a router will return a default 404 response instead. This behavior can be overridden with the notFoundHandler constructor parameter.
• Breaking: Remove deprecated Router.handler getter. The router itself is a handler.

• Update Router.mount parameter to accept a Handler.
• Make Router to be considered a Handler.
• Deprecate the Router.handler getter.

• Added @sealed annotation to Router and Route.

• Always register a HEAD handler whenever a GET handler is registered. Defaulting to calling the GET handler and throwing away the body.

• Use Function instead of dynamic in RouterEntry to improve typing.

• Fixed description to fit size recommendations.

• Initial release