All Versions
Latest Version
Avg Release Cycle
101 days
Latest Release
1517 days ago

Changelog History
Page 1

  • v5.2.2 Changes

    April 24, 2020

    ✅ Just adding a helper function to assist in writing handler tests.

  • v5.2.1 Changes

    April 17, 2020

    The internal contextData type now uses a pointer receiver to avoid copying it on every access. Also added a ContextRoute helper method to directly extract the Route string if that's all you need. Thanks again to @stuartclan for the help!

  • v5.2.0 Changes

    April 16, 2020

    🌲 This is mostly to allow logging middleware to show the actual route matched without expanded wildcards.

    Request context data can now be accessed using httptreemux.ContextData(r.Context()), which returns an interface ContextRouteData containing the parameters and the route path. The old ContextParams method is no longer recommended, but will continue to exist and work as before.

    Thanks to @stuartclan for the suggestion and help with the implementation and review!

  • v5.1.0 Changes

    April 11, 2020

    📚 Middleware is now officially supported. Documentation coming soon. Many thanks to @vmihailenco for the PR and @kravemir for help with the review!

  • v5.0.2 Changes

    December 18, 2018

    🚀 No code changes. This release just adds support for Go Modules. Thanks @SamWhited for the PR!

  • v5.0.1 Changes

    February 13, 2018

    When redirecting from a URL like /The%20Path/, the URL was incorrectly escaped again, redirecting to /The%2520Path.

    Thanks to @Backfighter for the detailed bug report!

  • v5.0.0 Changes

    October 11, 2017

    Go 1.7 and below continues to use UrlUnescape. I bumped the major version since this is a breaking change, but I doubt anyone will complain.

  • v4.1.0 Changes

    October 02, 2017

    📦 This function assists package clients in writing unit tests. It simply adds the given params map into a Context object at the internal params key.

  • v4.0.1 Changes

    August 02, 2017

    🔒 MethodNotAllowedHandler can access the handler map to generate the list of allowed methods, so it needs a read lock around it when new routes are being added during runtime. Operation without SafeAddRoutesWhileRunning was not affected by this bug.

  • v4.0.0 Changes

    June 21, 2017

    🚀 #52 had a need to be able to see if a route exists in the router, without necessarily serving it or responding with an error when it doesn't exist. This release adds that functionality.

    The breaking change is from #50, which changes ParamContextKey, used for fetching a Request Context's parameters from an exported string, to an unexported variable/type. You should have been using the ContextParams function instead of this variable anyway, so it is unlikely that any changes will be required. Thanks to @bontibon for suggesting this change.