feat: added blacklist functionality for auto aliases #361
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
icebob
requested changes
Feb 3, 2025
|
sorry for the delay and the poorly made PR in the first place. I should have checked the content / changes of my commit before creating the PR which i didnt and therefore didnt realise that my auto-formatting sort of re-formatted the whole codebase... its fixed now :) |
icebob
requested changes
Feb 17, 2025
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.
moleculer web already has a whitelist option for the auto alias functionality, but it lacks a blacklist functionality.
In which use case is this needed?
We have multiple services that act as gateways, each mapped to a different subdomain and each of them should only list relevant routes, doing this with whitelist becomes extremely cumbersome when you create more than a handful of services.