I think it is a very good start :), eventually we have to come up with second version of the filetree format as the current one has a major limitiation: categories are stored in the method source
Impact: - md5 hashes of the pure ST method sources do not correspond the md5 hashes in the git repository
But, knowing the filetree format, you could rebuilt the correct md5, no?
Oups, finally, I'm not impressed by your idea of trying to second guess git hashing :(
I like the fact that I can do git log --pretty="%H" path_to_method_file, and I have all the hashes I need.
yeah but you have the "wrong" hash as the source includes the category :) I prefer storing the methods in subfolders which represent categories, so I keep the methods sources as clean as possible. For instance this way a recategorization is detected as a move by standard git tools. Now that I say, we should do the same for the classes :P. Anyway, right now this is mostly a detail, more importantly we need make sure the image-side workflow is good :), so I am really happy that you push it
- each file-in requires another strip-the-category-path
?
=> typo, should be, strip-the-category pass :)