Assignment 6: Serverless fetching of leetcode questions

[chunweii]

Idea: Serverless function on Google Cloud Functions

0. Serverless function periodically (maybe once a week) calls https://leetcode.com/api/problems/algorithms/ to get all algorithms problems on leetcode, filter to make sure that the problems are not paid-only, then split them into their difficulties.
1. Store all of their question-slug and difficulty in a database.
2. When user chooses to attempt a new random leetcode question, another serverless function can be called,
3. Serverless function picks a random leetcode question-slug from the database and makes the graphql api query
4. Serverless function creates a new question using question-service, with the new leetcode question. The author of the question would be a special user "leetcode"
5. Serverless function returns the newly created question object to the user.

We can get all algorithm problems (including their title slugs and difficulty) using https://leetcode.com/api/problems/algorithms/. Make sure that the problem is not paid-only!

We can use the following graphql query on https://leetcode.com/graphql

query ($titleSlug: String!) {
    question(titleSlug: $titleSlug) {
        questionId
        title
        titleSlug
        content
        difficulty
        exampleTestcases
        topicTags {
            name
            slug
        }
        codeSnippets {
            lang
            langSlug
            code
        }
    }
}

[chunweii]

To be honest, the fetching of the question from leetcode can be done directly in question-service backend. And it makes more sense to do it that way rather than go through another layer of serverless functions

Alternatively, the only serverless function that we implement is the weekly update based on https://leetcode.com/api/problems/algorithms/.

[yhtMinceraft1010X]

Done in our A6 repo