-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optionally fix document when URL are redirected #1433
Comments
I looked at documentation and found nothing equivalent to this before opening the ticket. If it already exists please let me know, I will happily use it 😅 |
Interesting. Can you be a bit more specific on the details? From what I can tell, you'd like to fix URLs which get redirected. We have a |
Hi @mre Thanks for replying me Here is an example luong-komorebi/Awesome-Linux-Software#814 The whole PR is how fixing the URLs to their redirection. @ndsvw managed to do it by using his own homemade tool/script About the concept, the logic would be around a |
Just to clarify, the feature would replace the links in-line, right? So it would go and fix the links in the documents. |
Yes, that's the idea. So if someone mention http://www.google.com it would send to https://www.google.com http://oldsite.com => https://whatever.io Of course, it would not only affect domain redirection, but also page redirection. https://site.com/oldpage/ => https://site.com/section/#whatever This could help to identify things to fix. Then with a flag that could be |
I hope it's clearer @mre |
--remap
feature is greatBut it requires to add the source and target domain. So the feature is like what a "search and replace" would do.
I would like to see something that uses the power of lychee, and we could consider it would remap the URL in the document by replacing with the place they are redirected to.
@ndsvw achieved it by coding his own thing
luong-komorebi/Awesome-Linux-Software#810 (comment)_
I would like to see this ported to lychee.
I don't expect this to be enabled by default but something that could be enabled by a command-line parameter.
The text was updated successfully, but these errors were encountered: