I translated not yet translated keys and fixed one case where we used informal speech, because everywhere else formal speech is being used.
closes#1230
Fixes#1326
This PR moves all json in side_menu.json to common.json. We have an issue with the side menu layout as it's a high level component and this causes hydration issues with SSR when global namespaces are not passed by default.
Removed language.json translation file as we don't really need it anymore, just moved the couple of remaining items into tasks.json
I also reverted the change where I created lang_mismatch_lang and lang_mismatch_lang.explanation because we don't actually need two different strings and it was causing an issue where it would show a mix of english and the users language rather than just show the existing "Wrong language" text that is probably a better intermediate until the translations are updated. Let me know if there is a better way to handle updating the source english text for translations.
* Added flagged message table
* Added alembic migration and updated imports to match style
* Added GET endpoint to query all flagged messages
* Updates from linter
* Added POST endpoint for processing flagged messages
* Added pydantic interface model and fixed limit update bug
* fixed session in admin endpoint and added require session refresh for returned update
* removed unused import
* allow to export filtered by tree state and/or only prompts
* formatting
* add option to filter by lang code
* remove old export code
* export as list in only-deleted case
* website: show language in text area
When the language hasn't been detected (too little text) the langauge that it will be submitted as is shown. When we detect the language is not what will be submitted we show the detected language in red. The tooltip informs the user that they don't appear to be writing in the correct language.
Note: this replaces the modal dialog that we use to popup if the language appeared to differ.
* website: Don't suggest the user change the language
sanagnos