-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add check if commands of translated pages are different #10
Comments
Also, what about translated variables? It might always be a false positive, because, for example, |
We could also remove the contents of |
So in summary
Should we mark a page outdated if the abstract commands are the same as the one on the base page but aren't in the same order? |
I think instead of
Probably. |
Is this still something someone is working on? The number of examples doesn't say that much about being outdated, the contents of the commands do |
Hi, the issues is currently not being worked on but feel free to create a pull request to implement a better soluton. I don't have resources myself to create a soluton right now, maybe I can find time next year. |
In another tldr-repo, we achieved this (in Bash). |
Okay that's awesome. I'll put the task for reimplementing on my ToDo list but it may take one or two months until I find some time. |
If I had experience with Go, I'd probably would've worked on it, but I guess the Bash-example is a good start. In fact it is just removing all text in the commands that can be translated ( If you need any help, please let me know |
Additionally to checking if translated pages have a different number of examples, it would be awesome to show if the examples itself are outdated. This could be done by extracting all commands (basically lines starting and ending with
`
and removing all{{...}}
from them. The output of this operation should look the exact same on every translated page of a command.If a page has a different number of examples, that could be indecated with a ⚠ with red background and if the examples differ, with a ⚠ with yellow/orange background.
Edit: Actually replacing
{{...}}
with a default like{{argument}}
instead of removing it would be better because thencommand
wouldn't be the same ascommand {{...}}
The text was updated successfully, but these errors were encountered: