Superpowers, git and entries.json

[Ikalou]

​I just spent half an hour merging the "entries.json" file in git, and I didn't like it.

It's like trying to merge a scene, but even worse because it's global to the whole project. With scenes at least, you can copy them and experiment in your own "sandbox", or even lock them if your VCS supports that. Neither is an option for entries.json.

I understand that one of the strengths of superpowers is the ability to work collaboratively on a single server, but I can't be the only one that likes to use git and branches nonetheless. I gave it up with Unity a long time ago, but I had hoped superpowers would be more git friendly.

What do you think of the idea of using individual "meta" files for each asset instead of a global one?

I just wanted to raise the issue, feel free to close this if you don't think that should change.

[elisee]

Having individual meta files storing the info we have in entries.json seems like it could work? Would welcome a PR that does it along with migration. Would have to walk through the assets directory when loading a project and read lots of little files but I guess that's not a problem per se... would have to measure the impact.

@bilou84 anything you can think of that would break?

[bilou84]

Hmm, so actually the only data we need to store is the asset type? We can recover the id, name and children by going through the assets directory I guess.
We also need to store the latest used id to make sure we never use the same twice.

[elisee]

Just realized we kinda need the entries.json file to be able to order the assets in the tree. ... Although I guess we could store their order in their own metadata file, maybe? Seems like it could work.