Filename conflicts with composite primary keys
With some classes it happens that the same file name is used for different situations,
for example for class modTemplateVarTemplate and
primary:
- tmplvarid
- templateid:
we can have
templateId: 4 tmplvarid: 15
that will have the same file name as record with:
templateId: 41 tmplvarid: 5
and as a result just the second situation is saved into gitify.
It could be useful to add a key separator or something like that, thanks!
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Doesn't it put a ~hyphen~ dot in between the different parts of a composite key?
no, in the example above I have 415.yaml, but may be I'm missing something in configuration..