Article path calculation optimization #39
Merged
Conversation
This file contains hidden or 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
|
@aires-iris is attempting to deploy a commit to the cworld Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Your solution is right. Thanks for your distribution. |
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.
When obtaining the current path, the algorithm used is to intercept the content after the last
/This logic may cause bugseg: If the current article address contains multi-level directories, for example: www.domain.com/blog/devops/k8s-gateway-api, Using the current algorithm will cause the final calculated path value incorrectly include the content of the secondary path devops, making the prev/next article address invalid, resulting in 404
Considering that all article paths in the current project start with /blog, it is recommended to intercept the first two parts of the array to append the prev/next article
[subdirectory + article id], which is/blog/[subdirectory + article id]