Conditional middleware execution#370
Merged
A6dulmalik merged 3 commits intoMindBlockLabs:mainfrom Mar 26, 2026
Merged
Conversation
…into Conditional-Middleware-Execution
|
@shamoo53 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 PR: Add Conditional Middleware Execution (
unless&onlyFor)🧭 Overview
This PR introduces conditional middleware execution utilities that allow developers to selectively apply or skip middleware based on route patterns. This significantly improves developer experience (DX) by removing the need for complex guard-based workarounds.
🎯 Problem
In the current setup:
💡 Solution
Introduce two reusable helpers:
unless()→ skips middleware for specified routesonlyFor()→ applies middleware only to specified routesSupport flexible route matching using:
micromatch)🛠 Scope of Work
⚙️ Conditional Middleware Utilities
Created
src/middleware/utils/conditional.middleware.tsImplemented:
unless(middleware, patterns)onlyFor(middleware, patterns)(inverse logic)🔍 Route Matching Support
Added support for:
'/health')/^\/api\/v1/)'/api/**') usingmicromatch⚡ Performance Consideration
📦 Exports
src/index.tsfor easy consumption📊 Acceptance Criteria
unless(['/health'])skips middleware for specified routessrc/index.ts🧪 Testing
Added unit tests for:
unless()behavioronlyFor()behaviorAdded integration tests to verify:
📚 Usage Example
🏁 Summary
This PR adds a powerful and flexible middleware control layer, improving code clarity, reducing boilerplate, and enabling cleaner route-based logic in NestJS applications.
Closes #354
Closes #351
Closes #318
Closes #314