Samuel Stroschein

duplicate in linear https://linear.app/opral/issue/FINK-5/move-fink-manage-and-badge-to-changeset-based-deployment

Most interesting: Does having 60.000 messages files work? - git push - pull requests - initial import of a message (is the diff too strong) - will users raise concerns...

@martin-lysk interesting observation. The per-file splitting for version control would be great as can be seen in https://www.loom.com/share/6636f233340340d9b7f5e237c922592f. I was able to re-construct how message changes based on the diff,...

We should push for the one file per message approach to manifest our commitment to Lix. I had more thoughts overnight. If we have a one-file-per-message approach, we can directly...

> @janfjohannes lease plan this in a way that we can limit the number of files to 1000 per folder long term Where is this limitation coming from? @martin-lysk and...

> Should filenames represent the message name or the message id? - yes we have this question again ;-) Message id. We will/need to introduce keys/names as part of #1585....

### @martin-lysk thoughts after our call: - if we can introduce "aliases" in a simple manner (https://github.com/inlang/monorepo/issues/1585#issuecomment-1860875401), we can gain control over ids and persistence. - if we have control...

I do not see profound arguments against language splitting in storage. The arguments you mention regarding git are reasonable, but a) we need to hit a large scale until this...

@martin-lysk summary of the call: 1. go with your flatter structure but have a `v1` at the root to ease migrations ``` - project.inlang - messages - v1 - [part1]...

@martin-lysk @LorisSigrist Created the issue https://github.com/inlang/monorepo/issues/1920#issue-2048843732