Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO: Fix the Discourse Module #21

Closed
Sing-Li opened this issue Jan 12, 2022 · 3 comments · May be fixed by #73
Closed

TODO: Fix the Discourse Module #21

Sing-Li opened this issue Jan 12, 2022 · 3 comments · May be fixed by #73

Comments

@Sing-Li
Copy link
Member

Sing-Li commented Jan 12, 2022

Current Discourse module will keep populating the top ranking list to 10s or 100s of entries.

Re-implement the logic to select the TOP N entries - with N anywhere from 3 to 15 ONLY.

Define a "module structure" that makes sense for these sort of "full stack reactjs components", beware it will always be executing on nextJS (keep to JAMStack ideals).

Keep this work on ONE SINGLE PR.

@samad-yar-khan
Copy link
Contributor

@Sing-Li I would like to work on this issue. So we store the top N entries from the request in our CMS, repopulate them at intervals using cron jobs and make the top N entries accessible to the NextJS component depending on the parameters given to component ?

@RonLek
Copy link
Collaborator

RonLek commented Feb 4, 2022

@samad-yar-khan that's correct. If you see the current codebase, we have a cron function calling the fetchTopPosts function. Instead of storing all possible entries store only the top N within the CMS.

@samad-yar-khan
Copy link
Contributor

@RonLek Got it ! I will start working on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants