Page MenuHomePhabricator

Reuse more transaction construction code in bulk editor
ClosedPublic

Authored by epriestley on Jan 19 2018, 1:53 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jul 1, 8:46 AM
Unknown Object (File)
Thu, Jun 26, 8:04 PM
Unknown Object (File)
Tue, Jun 17, 12:38 AM
Unknown Object (File)
Mon, Jun 16, 6:45 PM
Unknown Object (File)
May 27 2025, 12:19 AM
Unknown Object (File)
May 27 2025, 12:06 AM
Unknown Object (File)
May 6 2025, 5:27 PM
Unknown Object (File)
May 5 2025, 6:12 PM
Subscribers
None

Details

Summary

Ref T13025. Currently, the bulk editor takes an HTTP request and emits a list of "raw" transactions (simple dictionaries). This goes into the job queue, and the background job builds a real transaction.

However, the logic to turn an HTTP request into a raw transaction is ending up with some duplication, since we generally already have logic to turn an HTTP request into a full object.

Instead: build real objects first, then serialize them to dictionaries. Send those to the job queue, rebuild them into objects again, and we end up in the same spot with a little less code duplication.

Finally, delete the mostly-copied code.

Test Plan

Used bulk editor to add comments, projects, and rename tasks.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable