New Version: v1.1.0 (HTTP.jl v1+ & Middleware update)

[ndortega]

Hello everyone,

This release has been a long time in the making and includes some major improvements:

• Now compatible with HTTP.jl v1.0.0+
• Added support for the new middleware chaining patterns (can now have global, router, and route-specific middleware)
• Removed all eval() calls from our macros so we can precompile the package
• Custom Response Serializers
• Fixed the generated docs layout

After upgrading the package to work with HTTP.jl v1+ this opened up a couple of opportunities to address the rest of the points in this list. The coolest improvement in my opinion is #2, which allows users to assign middleware at all levels. This feature alone makes it one of the few frameworks with this kind of flexibility.

You can read more about how to use router middleware in the guide:
https://ndortega.github.io/Oxygen.jl/stable/tutorial/bigger_applications/#Middleware-and-router()

[ndortega]

Quick update,

After re-reading those rules I thought of a more straightforward way to implement middleware flows. I already have a working prototype and am working on updating the docs to reflect this change in v1.1.1

Updated Middleware rules:

All middleware is additive, any middleware defined at the global, router, our route level will get combined
and get executed.

Regardless if set or not, Middleware will always get executed in the following order:

global -> router -> route 

Well, what if we don't want previous layers of middleware to run?
You set middleware=[], it clears all middleware at that layer and skips all layers that come before it.

For example, setting middleware=[] at the:

• global layer -> clears the global layer
• router layer -> clears the router layer and skips global layer
• route layer -> clears the route layer and skips the global & router layer (no middleware is run)

[ndortega]

I've just released these changes in today's patch v1.1.1

[ndortega]

@jiachengzhang1
Here's the updated middleware chaining logic