Drop the `Entity.string` and `Translation.string` fields
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 611
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 49
Description
Changes related to #3538, such as #4201 most recently, are moving Pontoon's internal representation of messages (both in their Entity source locale representation, and the Translation target locale representations) to rely on the value and properties JSON data model fields.
Once the Entity.string and Translation.string values are no longer required, they should be removed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Entity.string and Translation.string definitions and every reference to those fields, then inspect the changes related to #3538 and #4201 for the current value and properties model. Confirm that the fields are no longer required before removing them, and run the affected test suite to verify the JSON representations and translation workflows still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, localization
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100