alielbashir / blog Goto Github PK

Setup the Vue.js-based frontend with a project structure according to best practices

Different users should be able to do different things, which can be handled with scopes. Some users should be able to write new blog posts, while some others should only be able to read , according to their choice while registering.

• #7
• #8

scope will be encoded within the JWT's "roles" key

Posts router will include basic CRUD operations for blog posts

Endpoints

Create post

POST /api/posts

example request

{
    "title": "vscode tutorial",
    "content": "In this blog I'll be explaining how to use vscode, first step is to...",
}

example responses

HTTP status 201
HTTP status 401
HTTP status 403

Get posts

GET /api/posts

example response

{
    "posts": [
        {
            "title": "vscode tutorial",
            "id": 11,
            "creation_date": 1649212132,
            "username": "janedoe",
            "content": "In this blog I'll be explaining how to use vscode, first step is to...",
            "votes": 3
        },
        {
            "title": "codeblocks tutorial",
             "id": 131,
             "creation_date": 1649213057,
            "username": "johndoe",
            "content": "In this blog I'll be explaining how to use codeblocks, first step is to...",
            "votes": -26
        }
    ]
}

Delete post

DELETE /api/posts/{id}

example response

{"message": "post deleted successfully"}

Upvote/Downvote

POST /api/posts/{id}/upvote

POST /api/posts/{id}/downvote

example response

HTTP status 200
HTTP status 404

Add routes for user endpoints. User endpoints will be:

• POST /api/users/register {username: str, password:str} -> {username: str}
• POST /api/users/login {username: str, password:str} -> {token: str}

Connect frontend components to the API instead of using mock data

as seen in this and this workflow runs, the pytest step can fail sometimes where a bad request is registered for user login, and consequently other tests that may depend on user login.

Possible reason

Because the workflows run in parallel for 3.8 and 3.10 now, they can be running on the same database instance, which can cause conditions where a user is attempting to be registered that is already registered in the system, which can give back a 400 error.

Possible fixes

• Use different databases for different workflow runs
• Run the workflows in a sequence so they're not doing DB operations concurrently.

Write the code for the frontend components using strategy similar to think in react or vue equivalent