Closed Samuel-Therrien-Beslogic closed 4 weeks ago
Based on #256 to ensure no accidental DB changes, merge that one first Done
Please review/test carefully
Also based on discussions in: https://teams.microsoft.com/l/message/19:cf99fa441a694ba4a1377165cc4bd7a6@thread.tacv2/1727806176316?tenantId=cd34c2c6-a4f8-4af1-bdd5-497e97626cae&groupId=167b0d82-f8ec-429e-944f-45e9c370f2e3&parentMessageId=1727806102415&teamName=Beslogic%20-%20ARBRES%20Philanthropy&channelName=Pull%20Requests&createdTime=1727806176316 Original question:
Should all the *Internationalization classes/models be merged as the existing Internationalization ? I don't really see the need to split it up into multiple tables. If so, I could then also simplify the serializers that handle translations.
*Internationalization
Internationalization
Based on #256 to ensure no accidental DB changes, merge that one firstDonePlease review/test carefully
Also based on discussions in: https://teams.microsoft.com/l/message/19:cf99fa441a694ba4a1377165cc4bd7a6@thread.tacv2/1727806176316?tenantId=cd34c2c6-a4f8-4af1-bdd5-497e97626cae&groupId=167b0d82-f8ec-429e-944f-45e9c370f2e3&parentMessageId=1727806102415&teamName=Beslogic%20-%20ARBRES%20Philanthropy&channelName=Pull%20Requests&createdTime=1727806176316 Original question: