Update dependencies to fix machine translation#674
Conversation
Pull Request Test Coverage Report for Build 23796069142Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
d3807e3 to
840feba
Compare
|
I'm not really happy with a "fix machine translation" PR to also perform a major Wagtail upgrade and update linters and formatters (and thus also apply several changes to the code), especially since in the past we frequently had severe issues after major Wagtail upgrades |
|
The translation was not working because Deepl made changes to their API we had to update wagtail localize to a newer version (briefly described in #673). |
Yes, that's what I wanted to imply |
840feba to
b85bf16
Compare
…tion' into fix-machine-translation
|
Even after 0ebfbc4, the lockfile still contains more changes than it should, but I won't care about this, since no major versions have been changed, so everything should still be compatible. However, I noticed a bug regarding translations after the update: Clicking the "Translate" button activates the text box for the wrong snippet. Working with the dummy data ( myhpi.webmI think this is related to #614, since the translated string is inserted into the heading anchor on the page |
Removed commented-out setup for PostgreSQL in CI workflow.
styrix560
left a comment
There was a problem hiding this comment.
did not test, but code looks good given that we only reverted one commit and updated some other stuff.
account not available right now :c
No description provided.