Page MenuHomePhabricator

Allow older, invalid project tags to continue to function
ClosedPublic

Authored by epriestley on Jan 18 2016, 4:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 21, 1:34 AM
Unknown Object (File)
Wed, Dec 18, 1:06 AM
Unknown Object (File)
Wed, Dec 18, 1:06 AM
Unknown Object (File)
Mon, Dec 16, 8:09 PM
Unknown Object (File)
Fri, Dec 13, 10:18 PM
Unknown Object (File)
Wed, Dec 11, 11:58 PM
Unknown Object (File)
Sat, Dec 7, 11:00 AM
Unknown Object (File)
Sat, Dec 7, 10:26 AM
Subscribers
None

Details

Summary

Ref T10168.

Around October 12, T9551 made project hashtags stricter and prevented them from containing characters like comma (,).

Around December 27, D14888 changed how hashtags queries work so that the query does normalization instead of requiring the caller to normalize.

After the Dec 27 change, projects from before Oct 12 with now-invalid hashtags will no longer load when queried directly by hashtag, because the page queries for old,[silly]hash,,tag or whatever, it gets normalized into old_silly_hash_tag, and then there are no hits.

Instead, at least for now, query by both the exact raw text and the normalized hashtag. This should keep older stuff working until we can give users more support for migrating forward.

Test Plan
  • Forced a project to have a bogus hahstag.
  • Before patch: clicking its tag 404'd.
  • After patch: clicking its tag now works.
  • Visited a project by alternate hashtag.
  • Visited a project by denormalized hashtag and alternate hashtag (e.g., capital letters instead of lowercase letters), saw it redirect/normalize properly.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Allow older, invalid project tags to continue to function.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Jan 18 2016, 5:00 PM
This revision was automatically updated to reflect the committed changes.