Page MenuHomePhabricator

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

Authored by epriestley on Feb 13 2019, 5:24 PM.
Tags
None
Referenced Files
F22732802: D20162.id48163.diff
Sun, Oct 4, 7:38 AM
F22621505: D20162.id48141.diff
Tue, Sep 29, 4:39 PM
F22517773: D20162.diff
Sun, Sep 20, 10:32 AM
Unknown Object (File)
Aug 18 2026, 8:41 AM
Unknown Object (File)
Jul 30 2026, 2:13 AM
Unknown Object (File)
Jan 9 2026, 11:57 PM
Unknown Object (File)
Dec 4 2025, 12:46 PM
Unknown Object (File)
Nov 13 2025, 11:50 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
Branch
uri7
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 21985
Build 30029: Run Core Tests
Build 30028: arc lint + arc unit

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.