Page MenuHomePhabricator

Fix some "URI->alter(X, null)" callsites
ClosedPublic

Authored by epriestley on Feb 13 2019, 5:24 PM.
Tags
None
Referenced Files
F19507924: D20162.diff
Fri, Jan 9, 11:57 PM
F19097199: D20162.diff
Dec 4 2025, 12:46 PM
F18960423: D20162.diff
Nov 13 2025, 11:50 AM
F18872770: D20162.diff
Nov 5 2025, 6:09 AM
F18834969: D20162.diff
Oct 26 2025, 12:24 PM
F18816571: D20162.id48141.diff
Oct 21 2025, 7:45 AM
F18786003: D20162.id.diff
Oct 14 2025, 4:38 PM
F18750571: D20162.id48163.diff
Oct 4 2025, 8:15 AM
Subscribers
None

Details

Summary

Ref T13250. This internally calls replaceQueryParam(X, null) now, which fatals if the second parameter is null. I hit these legitimately, but I'll look for more callsites and follow up by either allowing this, removing alter(), fixing the callsites, or some combination.

(I'm not much of a fan of alter().)

Test Plan

Browsing a paginated list no longer complains about URI construction.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

There are no more explicit ->alter(X, null) callsites so I'm likely to let sleeping dogs lie for now. I'd like to gradually replace all alter() callsites but don't want to tempt fate too much given how much refactoring is already in this upcoming release.

This revision is now accepted and ready to land.Feb 13 2019, 6:38 PM
This revision was automatically updated to reflect the committed changes.