Open 0xjessel opened 12 years ago
/chat/unitiiidin and /chat/u3dining would be the same place. As soon as #5 is done, we can normalize location names to a consistent identity, which then we could map to a friendly name.
for example:
great, this is exactly what we need
Waiting on discussion for #52
@meltedxice see if you'd still like this issue to stay open after my latest changes be7d018a267de3fe4810188ce73ed2dabf89906a
just tested and it looks awesome. i would like one more thing before we close this issue, is to do a pretty/abbreviated version for some of the buildings (e.g. 'rsf')
where's wurster?
why does betchel engineering center suggestion disappear after 'betchel eng' (works up to the n, then typing g disappears)
Some locations have hard coded locations because Google maps can't find it. Those buildings never go through an api call so we don't have its full name. Maybe I'll have to hard code the title too.
Similar to #5, for our chatroom recommendations via geolocation, we need cleaner names on the client-side.
Currently we have text getting returned to the client like "UNIT III DIN", "UNIT II CNTL", "UNIT I CHRST".
Keeping in mind that we currently use the text values as the chatroom names we either need a mapping between the raw text value to a friendlier chatroom text OR a complete refactoring of the db to cleaner names, such as "u3dining". That way, the chat url would be /chat/u3dining (no spaces).
We also still need to think about the client-side whether we want to prettify the chatroom titles so that on the navbar and the h2 title says something like "ee40" instead of "EE 40".