-
Notifications
You must be signed in to change notification settings - Fork 36
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 translation coverage row to dashboard #3129
Add translation coverage row to dashboard #3129
Conversation
Do you have a reason why you choose a different approach then |
Ah sorry, I overlooked the point about AJAX |
201d766
to
0c35cb1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thank you! I decided to approve this PR even though I am not 100% sure if the calculation of the number of missing pages can be improved upon. I've added my try below, but feel free to ignore it!
40b30ce
to
a5ca153
Compare
a5ca153
to
1de6db4
Compare
@jarlhengstmengel I think this PR is ready for review again :) |
There are still a few inconsistencies in the data. Therefore @jarlhengstmengel and I will do some more testing and that's why I converted this to a draft PR |
@jarlhengstmengel I refactored the calculation for the translation coverage and now I get the correct calculations for the translation_count. Could you please check if it also works for you? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for the work! Now the count is working as expected!
f3a4b77
to
87c6469
Compare
87c6469
to
f39f605
Compare
Short description
This PR adds the translation coverage row to the dashboard. This branch is already quite old and needs a bit of an update, however I finally wanted to open up this PR to get some feedback in advance
Proposed changes
Side effects
Uff... the calculation doesn't seem great. Is someone aware of a better way to do it?Resolved issues
Fixes: #4
Pull Request Review Guidelines