Show related hashtags on bottom of search result page about loklak_search

[gupta-utkarsh]

Then yeah let us do it now as it is very likely that it might be used by some other component. Ill file a PR asap. 👍

[hemantjadon]

@mariobehling
Do we want the hashtags related to the search term here ??

[mariobehling]

Do we want the hashtags related to the search term here ??

Either related to the search term or related to the tweets of the search output, e.g. show hashtags that appear in the search results.

@Orbiter: How can we get this from the API?

[mariobehling]

The best is to collect the hashtags from the search results and display them on the bottom of the page.

[gupta-utkarsh]

Hi! @mariobehling can I work on this issue?

[gupta-utkarsh]

Thanks! @mariobehling I am thinking of showing hashtags that appear in the search results.. They are present for every feed result at this route. http://api.loklak.org/api/search.json?q=fossasia

[hemantjadon]

@uttu357 This will be nice start :)
Accumulate all the hashtags used in all the results along with frequencies and then show them in sorted order at the bottom.

Use ES6 syntax if possible :)

[gupta-utkarsh]

Sure! 👍

[hemantjadon]

This issue is fixed for a start in the above PR #127. Now what we can work on this issue is making the hashtags as sort of redux state. That is with each element when it arrives we also save the
The hashtags also which come with it.

What do you think @uttu357 ?

[gupta-utkarsh]

Making hashtags as sort of redux state is necessary and helpful when multiple components need them as is the case with the API Results and Query. If such a use case arises then we can move it and save it as a redux state?

Your thoughts? @hemantjadon

[hemantjadon]

Well yeah right now there is only this component making use of the hashtags.
But this seems like the application component is keeping a slice of the data (computed from the state) and making a sort of personal state. Which should not be the case with a presentational component. Also it seems very likely that this hashtag data might be used by some other component.
We can maybe delay this for now, but eventually the state needs to move to store. So we can make a call here do it now or let the need arise and then do it later.

All opinions are welcomed :)

[hemantjadon]

@uttu357 Sure :) Cheers :)