Automatic ID for elements

[christianseel]

When adding files from the filesystem you don't know the correct next ID for the element. It would be a nice feature if you're allowed to leave the ID empty and on Gitify build it would look up the correct next ID and add it automatically (to the db and the actual file).

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Mark-H]

Somewhat related to what I wrote at #69 (about merging, and dealing with ID conflicts).

[hugopeek]

When you give all your new elements an ID of 1 (or any existing ID will do I guess) and use the --no-cleanup flag when building, it seems to be auto-incrementing the IDs properly for each resource:

Building content from content/...
- Building admin context...
- Building global context...
  \ Primary Key Conflict found: modResource {"uri":"forms\/registration*","context_key":"global"} has the same primary key as {"uri":"home","context_key":"web"}
  \ Primary Key Conflict found: modResource {"uri":"forms\/contact*","context_key":"global"} has the same primary key as {"uri":"home","context_key":"web"}
- Building romanesco context...
- Building notes context...
- Building web context...
- Building hub context...
  \ Primary Key Duplicate found: duplicate modResource with primary {"uri":"status\/kanban","context_key":"hub"}
  \ Primary Key Duplicate found: duplicate modResource with primary {"uri":"backyard\/examples\/foundation","context_key":"hub"}
- Attempting to resolve ID Conflict for {"uri":"home","context_key":"web"} with 4 duplicate(s).
  \ Duplicate #1: resolving primary key conflict by building object with new auto incremented primary key. 
  \ Duplicate #2: resolving primary key conflict by building object with new auto incremented primary key. 
  \ Duplicate #3: resolving primary key conflict by building object with new auto incremented primary key. 
  \ Duplicate #4: resolving primary key conflict by building object with new auto incremented primary key. 
- Re-extracting content; you will need to commit the changes manually.
  \ Extracting content into content (275 resources across 8 contexts)...
  \ - Extracting resources from admin context (25 resources)...
  \ - Extracting resources from backyard context (0 resources)...
  \ - Extracting resources from global context (16 resources)...
  \ - Extracting resources from hub context (147 resources)...
  \ - Extracting resources from mgr context (0 resources)...
  \ - Extracting resources from notes context (3 resources)...
  \ - Extracting resources from romanesco context (35 resources)...
  \ - Extracting resources from web context (48 resources)...
  \ Done! Time: 2,024ms | Memory Usage: 39.07 mb | Peak Memory Usage: 67.29 mb
  \ Clearing cache...
Done! Time: 14,887ms | Memory Usage: 39.29 mb | Peak Memory Usage: 67.29 mb

I only tried it with resources.. You can't assign parent IDs in this case of course, so the new resources end up in root folder.