[FEATURE] Resolve shortcut destination #550
Open
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
Since a shortcut should not be encoded, but its destination, we want to resolve the id of the request to that of the shortcut. dmitryd#320
|
On a quick glimpse, this looks like a good solution and I'd definitely second the request to take this back into RealURL |
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.
According to issue #320, I would like to reintegrate shortcut resolving into the realurl feature pool.
Therefore the pagePath/dontResolveShortcuts configuration has been added again and set to TRUE by default, to not break existing realurl 2.x installations.