Resolving foreign keys about gitify HOT 2 OPEN

This is related to #6, however it's a slightly different use case. With the School use case it might make sense to use the method in #6 as each class room is only in one school, but resolving these relations could also be super useful for with other types of relations.

For example an editedby or createdby column - you don't want the user contained within that as per #6, but having the username instead of the ID per this issue would be super useful.

from gitify.

This would be great. The only tricky part is mapping changes, I think -- so if someone changes the key name (School ABC has been renamed to School CBA), how does that information get tracked back? That's the one advantage of using IDs.

Maybe it could be listed as School ABC (4), and then for storing it can just regex out that last integer. A couple of thoughts on how to handle various "user data entry" issues:

1. "School ABC" would create a new category, unless there's already a "School ABC" category; in that case, the next time gitify extract is run, it'd return "School ABC (4)". The tricky part here is what happens if multiple elements use just School ABC in one gitify build; as long as the category is created along with the first item, it should be fine, but if it somehow groups everything, we could end up with multiple School ABC categories (maybe?)
2. "4" would connect it to "School ABC"; the next time gitify extract is run, it'd return "School ABC (4)"
3. "School CBA (4)" could either change the category name to School CBA or leave it alone. In the former case, the next time gitify extract is run, we'd get "School CBA (4)" for all items with cat 4; in the latter, we'd still get "School ABC (4)". Up to you; I don't really know what the user expectation would be there. I think we almost have to leave it, though, because unless someone changes every element to "School CBA (4)", it's just going to get changed back by any elements that build later anyway.
4. "School ABC (3) (4)" would connect to ID 4; the regex should always grab the last int in parenthesis
5. "School ABC 4" would create a new category. The ID needs to be within parenthesis
6. "School ABC (5)" (where 5 is a different category) would connect it to the real category 5. Next time gitify extract is run, it'd return "Other Category (5)".
7. "School ABC (12)" (where 12 is a nonexistent category ID) would connect it to ID 4 -- the real School ABC category
8. "New Category (12)" (where 12 is a nonexistent category ID and New Category is a nonexistent category name) would create a new category, which may or may not be ID 12. The real ID would be returned with the next gitify extract.

That's all for now :p

from gitify.