Case sensitivity on hashtags
Summary
Case sensitivity on hashtags is detrimental to the users experience.
Steps to reproduce
Compare the following two links and note the hashtag params difference in case.
- https://www.minds.com/newsfeed/global/top;hashtag=unfucktheworld;period=24h
- https://www.minds.com/newsfeed/global/top;hashtag=UnfuckTheWorld;period=24h
Platform information
Cross-platform web.
What is the current bug behavior?
examples, #FOObar and #fooBAR are not showing the same hashtags.
What is the expected correct behavior?
Case sensitivity shouldn't make a difference for hashtags.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
added Priority::2 - Normal Sprint::09/25 - Oldfashioned Owl Type::Bug scoped labels
changed weight to 2
Suggestion: Whenever user or anyone adds or edits a hash tag, when the hash tag is saved and displayed, force hash tag to all uppercase.
changed time estimate to 3h
added Sprint::10/09 - Pink Panther scoped label and automatically removed Sprint::09/25 - Oldfashioned Owl label
changed title from (fix): Case sensitivity on hashtags to Case sensitivity on hashtags
added Status::Backlog scoped label
- Owner
@benhayward.ben this should be as simple as forcing the
;hashtag=
in the pipe to lowercase. added Status::InProgress scoped label and automatically removed Status::Backlog label
moved to front#2088
added Status::Review scoped label and automatically removed Status::InProgress label
added 30m of time spent at 2019-10-14