indra4837/pokemon

Hi there 👋

• 🔭 I’m currently working on web development in React and NodeJS and am interested in backend development
• 🌱 I’m currently learning microservices
• 👯 I’m looking to collaborate on web development (frontend)
• 💬 Ask me about computer vision
• 📫 How to reach me: [email protected]
• ⚡ Fun fact: i'm a carnivore

pokemon's Issues

US2: Querying data from database

As an API user, I want to perform operations to browse, filter and sort fields based on queries

Acceptance Criteria:

• Queries return a list of items that support pagination
• List sorted by id

Task - Documentation

As a developer and user, I want to know how to use the API endpoints and what parameters to pass.

Acceptance Criteria:

• Clear and concise documentation of API endpoints, parameters available and method type

Bug - Wrong Date Format and None Object error

Issue Description

1. Date format is not in required format (DD-MM-YYYY)
2. During GET request on route /trainer, if trainerId doesnt exist, None Object error recevied and error is not handled

Steps to reproduce

1. Date issue
   a. Perform GET request on /trainer or /pokemon route and see response

2. None Object Issue
   a. Perform GET request on /trainer/?trainerId=trainerId route with a trainerId that doesnt exist in database

Task - Refactor codebase

As a developer of the codebase, I want to easily find the functions and tests written in an organized manner

Acceptance Criteria:

• Files and code organized in functional structure (based on what they do)

US4: CRUD operations

Description

As an API user, I want to create, read, update and delete trainer and pokemon data.

API endpoints:

Trainer

• /trainer/delete?trainerId={trainerId}
• /trainer/create?id={id}&firstName={firstName}&lastName={lastName}&dateOfBirth={dateOfBirth}
• /trainer/update?id={id}&firstName={firstName}&lastName={lastName}&dateOfBirth={dateOfBirth}

Pokemon

• /pokemon/delete?pokemonId={pokemonId}
• /pokemon/create?id={id}&nickname={nickname}&species={species}&level={level}&owner={owner}&dateOfOwnership={dateOfOwnership}
• /pokemon/update?id={id}&nickname={nickname}&species={species}&level={level}&owner={owner}&dateOfOwnership={dateOfOwnership}

Acceptance Criteria:

• on delete, cascade to relations as well
• validate data and handle exceptions

US1: Seeding database

As an API user, I want to store the data permanently by uploading CSV files so that I can access them in the future to do other operations

Acceptance Criteria:

• Should be able to handle large file sizes (< 1GB)
• Validation on uploaded data
• Upload CSV as a single transaction
• Update database if id already exists

US3: Exchange

As an API user, I want to perform exchanges of Pokemon between different users

Acceptance Criteria:

• Each Pokemon has a history that shows history of trainers
• Exchange as a transaction