Adding the ability to use path-match in the whitelist array #9
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.
Scenario
Imagine having a website where part of the site is dynamic but still required to be public (not requiring authentication) Currently this would require manually restarting/editing the
whitelist
option since it is a simple string check. This is somewhat possible by setting the top level path/some/path
allowing public access to all of the subpaths beyond that (e.g./some/path/that/is/open
)I have a situation where I need to protect information about our customers, so sharing the entire collection
/merchant
is not feasible. I also want to allow public access to the clients menus,/merchant/X/menu
but I cant do this with the whitelist today.Changes
I've added the
path-match
library to enable parameterized whitelabel, essentially wildcard whitelabels.