feat: support regular expressions in routeBlacklist values #98
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #98 +/- ##
==========================================
+ Coverage 98.82% 98.85% +0.02%
==========================================
Files 2 2
Lines 170 174 +4
Branches 70 73 +3
==========================================
+ Hits 168 172 +4
Misses 1 1
Partials 1 1 ☔ View full report in Codecov by Sentry. |
github-actions bot
pushed a commit
that referenced
this pull request
Dec 19, 2023
## [10.5.0](v10.4.1...v10.5.0) (2023-12-19) ### 🚀 Features * support regular expressions in routeBlacklist values ([#98](#98)) ([fabf6d7](fabf6d7))
|
Thanks for contribution! And sorry for late review, but it should be released soon. |
|
🎉 This PR is included in version 10.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
FIrst of all, thanks for the library :)
I thought it would be useful to support regular expressions in
routeBlacklistproperty values. One might need to blacklist a set of subpaths under a base path, e.g. when using @fastify/swagger-ui it would be useful to blacklist all of the exposed subpaths from being collected (JSON documentation, YAML documentation, and so on).