Improve matchPathFilter to handle mixed arrays of string and glob paths #1050
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.
Description
The matchPathFilter function has been enhanced to handle mixed arrays of string and glob paths. This allows for more flexible URI matching, accommodating cases where both types of paths are specified in the same array.
Motivation and Context
This change is necessary to improve the functionality of the matchPathFilter function. Previously, it did not support arrays containing both string and glob paths, which could lead to unexpected behavior or failed matches. This enhancement addresses that limitation, allowing developers to utilize mixed path types seamlessly.
Error: [HPM] Invalid pathFilter. Expecting something like: ["/api", "/ajax"] or ["/api/", "!.html"]
How has this been tested?
The changes were tested with various scenarios, including:
Testing was performed in a local development environment and validated against existing unit tests for regression.
Types of changes
Checklist: