Original PR had issues in the CI when building.
> Refactor of the Validation System for more ease of use in the future.
The project now builds a standalone executable and executes it before
the main project is built or published.
Since it is now a standalone executable we are also able to use .NET
Core features as we are no longer locked to netstandard.
> The project currently includes 1 task, LocalesValidationTask, that
will check if the locales.json file has any of the following issues:
> - The json is invalid.
> - The json has locales with missing languages.
> - The json has locales with langauges that are just duplicates of the
en_US field.
> If the project is built or published locally it will also fix any
missing languages or duplicate fields.
---------
Co-authored-by: LotP1 <68976644+LotP1@users.noreply.github.com>
Refactor of the Validation System for more ease of use in the future.
The project now builds a standalone executable and executes it before
the main project is built or published.
Since it is now a standalone executable we are also able to use .NET
Core features as we are no longer locked to netstandard.
The project currently includes 1 task, LocalesValidationTask, that will
check if the locales.json file has any of the following issues:
The json is invalid.
The json has locales with missing languages.
The json has locales with langauges that are just duplicates of the
en_US field.
If the project is built or published locally it will also fix any
missing languages or duplicate fields.
---------
Co-authored-by: Evan Husted <gr33m11@gmail.com>
Co-authored-by: Evan Husted <greem@greemdev.net>
Use 1 locales file instead of individual files for each langauge.
This makes it easier to keep track of what is missing.
The PR will automatically fix missing locales and throw an error if
anything is incorrect, by running the emulator. That way the person
adding a new locale or new language can just run the emulator once to
populate all the fields, so they can easily begin translating.
