Is your feature request related to a problem? Please describe.
Yes -- the problem is that for performance reasons we don't have the server to have to parse old messages to look for hashtags. We create the hastag record when the message is made, so why would we be going back through and fetching it?
Describe the solution you'd like
I think it makes sense to add a GET /api/v1/hashtag/:hashtag endpoint to fetch the stats. We can do this asynchronously on click by the UI.
Describe alternatives you've considered
We could go through and parse individually on server, which would make stats show up synchronously.
Is your feature request related to a problem? Please describe. Yes -- the problem is that for performance reasons we don't have the server to have to parse old messages to look for hashtags. We create the hastag record when the message is made, so why would we be going back through and fetching it?
Describe the solution you'd like I think it makes sense to add a
GET /api/v1/hashtag/:hashtag
endpoint to fetch the stats. We can do this asynchronously on click by the UI.Describe alternatives you've considered We could go through and parse individually on server, which would make stats show up synchronously.