Add option for user to choose which module logic to use

[Ni4rK]

My logic for modularized json files is different compared to what is shown in the examples directory :

• In example : locale = directory, module = file

— res
— — locale-de
— — —moduleA.json
— — — moduleB.json
— — locale-en
— — — moduleA.json
— — — moduleB.json

• In my project : locale = file, module = directory

— res
— —moduleA
— — —de.json
— — —en.json
— —moduleB
— — —de.json
— — —en.json

It could be nice to have a toggle in the plugin settings, so then we can choose which module logic we want to use.

[marhali]

I will use this ticket to reengineer the IO system.

New IO configuration

Folder-Strategy:

• flat (single-layer)
• modularized: namespace - locale
• modularized: locale - namespace

Parser-Strategy

• json
• yaml
• properties

File-Pattern-Strategy: (adjusts automatically when changing parser)

• .
• *.json and so on...

[marhali]

New flow: DataStore -> FolderStrategy -> ParserStrategy -> TranslationData

IOHandler

Constructor: FolderStrategy, ParserStrategy

• read: whole read process using configured strategies
• write: whole write process using configured strategies

FolderStrategy

Responsible for managing the local project structure for translation files (namespace, file-pattern)

• read: Locales Path -> Locales / Modules -> VirtualFile -> ParserStrategy -> TranslationData
• write: TranslationData -> Modules / Locales -> ParserStrategy -> VirtualFile

ParserStrategy

Parses the actual translation files

• read: VirtualFile -> locale & (namespace) -> TranslationData
• write: TranslationData -> locale & (namespace) -> VirtualFile

[marhali]

You can configure your preferred folder structure with the next release. Don't forget to star this repository 👍

[Ni4rK]

Thank you for quickness ! 😎 ❤️