.inlang folder to avoid multiple files and enable caching

[samuelstroschein]

problem

Proposal

Introduce a .inlang folder which serves as a (single) inlang project.

- .inlang
  - cached-modules/
     - jsdelivr.com/npm/plugin.inlang.messageFormat.js
  - settings.json
  - ... other files

Pros

• the .inlang directory can be extended as required without convoluting developers repositories with additional files
• directory structure could serve as an incremental step towards proper my-project.inlang files which are usually just zipped directories

Cons

• another change... we should likely wait until this issue becomes really pressing to a) be certain about this change and b) minimize the risk of wrong decisions

[samuelstroschein]

Proposal - .inlang directory with storage

Modules get their own directory where they can store whatever they. For example, parrot stores what has been reviewed or not. The inlang message format plugin stores the messages, and paraglide js stores the compiled output.

Pros

• modules can store anything they need in a project

Cons

• massive exposure of fs, arbitrary data content, and more.
• how to do merging of data, real time collaboration, etc ?

- .inlang
  - settings.json
  - app.martinLysk.parrot
    - reviews.json
    - screenshots/
       - message-294ns.png
       - ...
  - plugin.inlang.messageFormat
    - messages.json
  - ...

const project = await loadProject()

project.fs.readFile("app.martinLysk.parrot/reviews.json")

[samuelstroschein]

Nice idea but let's wait for the requirements of storing screenshots etc to emerge. A simple key-value store seems sufficient. Although even a KV store raises "how to merge this" questions.

[NilsJacobsen]

another change... we should likely wait until this issue becomes really pressing to a) be certain about this change and b) minimize the risk of wrong decisions

I agree, I vote for waiting. Even tough I think it's gonna make sense in the future.