-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(condo): added the ability to translate classifiers #5591
base: main
Are you sure you want to change the base?
feat(condo): added the ability to translate classifiers #5591
Conversation
First, I retrieved the classifiers for place, category, and problem using this script.
All responses were saved into the following files: ticketProblemClassifiersApi.json ticketCategoryClassifiersApi.json |
|
Hi, thanks for the PR. Overall it looks ok 🏅 , but we need to solve 1 issue: how to migrate existing databases where fields are written in strings... |
Next, I compiled all the Russian translations into a file named ru.json and verified that everything was included and nothing was missing.
|
As the penultimate step, I wrote a script to update the database using SQL.
|
The final step is to run this script to update the fields in the database.
|
Thank you for the feedback! |
Yes, it's possible to create migration based on the script :-) I'll check translation keys and implement a migration :-) Thanks for the PR |
@toplenboren Hello! Thanks for your response! Any updates on the progress? |
@SavelevMatthew @toplenboren |
Hello!
I noticed that the platform lacked a feature for translating classifiers based on the selected language, so I implemented it.
To ensure everything functions correctly, you will need to migrate and update the classifier fields.
I'll provide a detailed explanation of the changes I made in the comments below.