docs(routing): add note about middleware returns

[oof2win2]

Better describe middleware and how returning within it behaves

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This improves on documentation. Before it stated that they should not return anything, which is untrue - returning from middleware returns the value as a response.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
nitro	Edit on Studio ↗︎	View Live Preview	9ebb232

[pi0]

Thanks!

[oof2win2]

Why is this not recommended to do? Unauthenticated reauests can be ended before they reach other handlers with this.

[pi0]

Yes, also this breaks the nitro request handling lifecycle (i am planning also to introduce defineMiddlewareHandler in h3 that essentially disallows return value as a convention)

[oof2win2]

Oh okay. Is there any method that would allow for this, to just directly respond to unauthenticated requests with 401s in one place?

[pi0]

You can throw an error like throw createError({ statusCode: 401 }) this will still preserve lifecycle and totally valid from a middleware or any composable. (if feel missing in docs, PR welcome to add this note ❤️ )