Page MenuHomePhabricator

Support HTTP parameter prefilling in EditEngine forms for CustomFields
ClosedPublic

Authored by epriestley on Dec 2 2015, 2:06 PM.
Tags
None
Referenced Files
F22637502: D14634.id35404.diff
Wed, Sep 30, 8:43 AM
F22620724: D14634.id.diff
Tue, Sep 29, 3:32 PM
F22620717: D14634.id.diff
Tue, Sep 29, 3:32 PM
Unknown Object (File)
Aug 26 2026, 10:21 PM
Unknown Object (File)
Aug 25 2026, 8:02 PM
Unknown Object (File)
Aug 24 2026, 1:18 PM
Unknown Object (File)
Aug 6 2026, 10:17 PM
Unknown Object (File)
Aug 3 2026, 6:38 AM
Subscribers
None

Details

Summary

Ref T9132. This allows you to prefill custom fields with ?custom.x.y=value, for most types of custom fields.

Dates (which are substantially more complicated) aren't supported. I'll just do those once the dust settles. Other types should work, I think.

Test Plan
  • Verified custom fields appear on "HTTP Parameters" help UI.
  • Used ?x=y to prefill custom fields on edit form.
  • Performed various normal edits.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Support HTTP parameter prefilling in EditEngine forms for CustomFields.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.

This has a couple of small pieces of "weird glue" (with comments noting weirdness) but I think it's fairly sane overall.

It's hard to just move directly to a good state because I can't change CustomFields too much until everything uses EditEngine, since if I do other applications (Maniphest, Differential, etc) will break. So I'm trying to get us like 95% good, with as little "weird glue" as possible, and hopefully clean that up later.

chad edited edge metadata.
This revision is now accepted and ready to land.Dec 2 2015, 4:56 PM
This revision was automatically updated to reflect the committed changes.