fix: make excludeRouters configurable instead of hardcoded #220
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.
Summary
When
excludeDexesis specified, the plugin previously added a hardcoded list ofexcludeRouterswithout any way to override or opt out. This PR makes the behavior configurable.Problem
Solution
Changes
excludeRouterstoFormPropswith JSDocexcludeRoutersto quote queryDEFAULT_EXCLUDED_ROUTERSconstantBackwards Compatible
Existing integrations work identically - the default behavior is preserved when
excludeRoutersis not specified.