ASCII export and import for Git #48

New Issue

2022-11-02T18:03:52Z

thorsten commented

2022-11-02 18:03:52 +00:00

(Migrated from devops.tsommer.org)

Description

Checking in the binary file gets problematic, when multiple developers working on different branches. Every time, it would result in a merge conflict. Hence, it should be possible to export (save) a project as ASCII file as well. Further, open a project from such an ASCII file must be possible as well.

When the user tries to open an ASCII file, a new binary file get created. Therefore, importing is the right term. I could use *.i18ng as file extension. This feature should be named "Git export" and "Git import". Also, there should be a config option to automatically maintain such a Git export.

Tasks:

Define the ASCII format. Should work with merges e.g. considering conflicting ids.
File extension: *.i18ng
Add the Git export setting
- Enable automatic Git export <yes/no>
- Git export directory <path>
- Git export name <filename>
- Export sensitive data like API keys?
Add a Git import option on the loading screen.
- Creates a binary file at the temp. directory.
- When importing, the automatic export gets enabled by default, which overwrites the existing file.

# Next N/A # Description Checking in the binary file gets problematic, when multiple developers working on different branches. Every time, it would result in a merge conflict. Hence, it should be possible to export (save) a project as ASCII file as well. Further, open a project from such an ASCII file must be possible as well. When the user tries to open an ASCII file, a new binary file get created. Therefore, importing is the right term. I could use `*.i18ng` as file extension. This feature should be named "Git export" and "Git import". Also, there should be a config option to automatically maintain such a Git export. **Tasks:** - Define the ASCII format. Should work with merges e.g. considering conflicting ids. - File extension: `*.i18ng` - Add the Git export setting - Enable automatic Git export `<yes/no>` - Git export directory `<path>` - Git export name `<filename>` - Export sensitive data like API keys? - Add a Git import option on the loading screen. - Creates a binary file at the temp. directory. - When importing, the automatic export gets enabled by default, which overwrites the existing file.

thorsten commented

2022-11-02 18:04:35 +00:00

(Migrated from devops.tsommer.org)

changed the description

thorsten commented

2022-11-06 19:27:08 +00:00

(Migrated from devops.tsommer.org)

I could use JSON as format
Solving the conflicting ids by using persistent GUIDs

- I could use JSON as format - Solving the conflicting ids by using persistent GUIDs

thorsten commented

2022-11-06 19:27:53 +00:00

(Migrated from devops.tsommer.org)

created branch 48-ascii-export-and-import-for-git to address this issue

created branch [`48-ascii-export-and-import-for-git`](/open-source/dotnet/i18n-commander/-/compare/main...48-ascii-export-and-import-for-git) to address this issue

thorsten commented

2022-11-06 19:27:58 +00:00

(Migrated from devops.tsommer.org)

mentioned in merge request !25