Add Good 1st Issue Filter

[harshraj8843]

• Update list of Good 1st Issue on click of a particular tag

codinasion.org/good1stissue

[Yarnacle]

We should probably start by implementing a filter on the backend side (so in the api repo instead of this one)

[harshraj8843]

I don't think so 🤔

• It will increase the API response time.
• Vercel only allows execution of functions for 3 Seconds only, after than function will fail

---

A better approach would be, to filter issues in frontend

Reference 👉🏻 https://github.com/codinasion/good-1st-issue/blob/78fdb9dd9d640530eff900fcfcd0a01931298aad/pages/index.js

[Yarnacle]

Since there isn't a massive amount of data, client side filtering may be better, actually.

I'm a little confused as to what the good1stissue part of the repo is for if it has its own repo? And shouldn't this issue be in the other repo?

[Yarnacle]

It seems like the backend of good-1st-issue is in its own repo but why is there an index.js in that repo with a react frontend and then a bunch of frontend components for good-first-issue on this repo?

[harshraj8843]

Actually, till now all projects were deployed on separate subdomains of codinasion.org

But it wasn't easy to maintain all project's websites separately

So, it is decided that all (most) of our projects will be hosted on codinasion.org (this repo)

---

Note Good 1st Issue Repo contains Website + Backend + Github App Code

Previously, Good 1st Issue was deployed on good1stissue.codinasion.org

Now, we are migrating frontend to codinasion.org/good1stissue

---

The backend of Good 1st Issue will also be migrated to Codinaion's centralized backend (later)

[harshraj8843]

https://good1stissue.codinasion.org/

https://codinasion.org/good1stissue