[00200200]

Summary

When Route.Queries receives an odd number of parameters, it previously set r.err and returned nil. Because callers use fluent builder chaining on *Route (such as r.Queries(...).Path(...).Handler(...) or checking r.Queries(...).GetError()), returning nil caused an immediate nil pointer dereference instead of preserving the error on the route.

This change:

• Updates Route.Queries to return r when parameter validation fails, consistent with Headers, HeadersRegexp, and other route builder methods.
• Guards Queries with if r.err == nil so pre-existing route errors are preserved without attempting redundant regexp additions.
• Adds unit tests verifying that chaining on odd query parameters does not panic, the error is recorded on the route, and routes with errors do not match incoming requests.

[00200200]

Closing, since this repository has not had any commits since mid-2024. Happy to reopen if it becomes active again.