This is a mildly obscure feature request for GCA5.
If the saved character files use ID values as the ones in GCA4 do, could they be globally unique rather than sequential?
I ask because the use of sequential values makes merges harder. If a character has been branched and that branch is then to be merged back into the mainline, it's very likely to have duplicate ID values, which not only won't be warned about by the VCS but need to be resolved manually.
(Yes, I keep my character files under version control. I recently used git bisect to find out exactly when a particular skill was acquired.)
(More generally, GCA should not be the only tool that can read GCA files; a more standardised format like XML/JSON/YAML would make life much easier for support software.)
If the saved character files use ID values as the ones in GCA4 do, could they be globally unique rather than sequential?
I ask because the use of sequential values makes merges harder. If a character has been branched and that branch is then to be merged back into the mainline, it's very likely to have duplicate ID values, which not only won't be warned about by the VCS but need to be resolved manually.
(Yes, I keep my character files under version control. I recently used git bisect to find out exactly when a particular skill was acquired.)
(More generally, GCA should not be the only tool that can read GCA files; a more standardised format like XML/JSON/YAML would make life much easier for support software.)
ID values in GCA
0 commentaires:
Enregistrer un commentaire