Version 1 vs 2
Version 1 vs 2
Edits
Edits
- Delete by epriestley, Version 2
- Feb 11 2017 9:53 PM
- Edit by rsmarples, Version 1
- Feb 11 2017 9:51 PM
Original Change | Most Recent Change |
Edit Older Version 1... |
Content Changes
Content Changes
Phabricator's remarkup creates handy links to objects from a one letter name followed by it's id.
While handy, this plays havoc when developers frequently refer to things in commit comments or discussions.
For example, DHCP has the values `T1` and `T2`, co-ordinates have `Z1` and indexes might have `I2`.
Because we want to achieve the same workflow regardless of the id in use, the easy solution is to start these objects incrementing their id from a higher number to decrease the chance of a collision.
Also, we don't want to escape this because some committers to a project might not be using Phabricator.
Lastly, we want to keep the Phabricator workflow as similar as possible, and just typing T101 to ref a ticket is actually quite handy.
Phabricator's remarkup creates handy links to objects from a one letter name followed by it's id.
While handy, this plays havoc when developers frequently refer to things in commit comments or discussions.
For example, DHCP has the values `T1` and `T2`, co-ordinates have `Z1` and indexes might have `I2`.
Because we want to achieve the same workflow regardless of the id in use, the easy solution is to start these objects incrementing their id from a higher number to decrease the chance of a collision.
Also, we don't want to escape this because some committers to a project might not be using Phabricator.
Lastly, we want to keep the Phabricator workflow as similar as possible, and just typing T101 to ref a ticket is actually quite handy.