Dean Ayalon
"By default, the Data Migration Tool sets the target file locale to the system on which the migration happens. However, the data migration tool actually does support specifying a locale as a CLI flag"
Since modules are their own solutions and code can break when running on the wrong locale, Devin should allow configuration of the module's locale (Perhaps also recognize it automatically), and retain it between clones and migrations
For example:
A solution of mine was created with the
en_IL
locale, but my Devin server was using
en_US.UTF-8
After migration, when running in a calculation context,
Date
functions were formatted as
MM/DD/YYYY
instead of
DD/MM/YYYY
You can imagine the chaos