[Experiment] Add glob redirects #1278
Open
+104
−11
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.
This is a concept PR that tries to add glob support to our redirect system using https://github.com/dazinator/DotNet.Glob.
With this change (which I couldn't test), we could use the following patterns:
Trailing Wildcard Redirects
Uses
**
to match all content under a path prefix.Example:
/reference/apm/agents/android/setup
→/reference/opentelemetry/edot-sdks/android/setup
Single Segment Wildcard Redirects
Uses
*
to match any characters within a single path segment.Example:
/guides/elasticsearch/intro
→/tutorials/elasticsearch/getting-started
Single Character Wildcard Redirects
Uses
?
to match a single character.Example:
/api/v1/user1.json
→/api/v2/users