Page MenuHomePhabricator

Separate commit message parsing and validation from Conduit
ClosedPublic

Authored by epriestley on Dec 14 2016, 4:05 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 19, 5:53 PM
Unknown Object (File)
Sat, Apr 6, 1:36 PM
Unknown Object (File)
Fri, Apr 5, 5:35 PM
Unknown Object (File)
Tue, Apr 2, 8:20 AM
Unknown Object (File)
Mon, Apr 1, 12:57 AM
Unknown Object (File)
Sat, Mar 30, 3:28 AM
Unknown Object (File)
Tue, Mar 26, 7:25 PM
Unknown Object (File)
Tue, Mar 26, 2:29 PM
Subscribers
None

Details

Summary

Ref T11114. I want to move this step away from custom fields. To start with, isolate all the parsing in one class with a clearer API boundary.

Next, I'll make this class use new field objects to perform parsing, without CustomField interactions.

Test Plan

Created and edited revisions from the CLI, using valid and invalid commit messages.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Better separate commit message parsing and validation from Conduit.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
epriestley retitled this revision from Better separate commit message parsing and validation from Conduit to Separate commit message parsing and validation from Conduit.Dec 14 2016, 4:13 PM
chad edited edge metadata.
This revision is now accepted and ready to land.Dec 14 2016, 4:48 PM
This revision was automatically updated to reflect the committed changes.