Steps to reproduce:

• Log in
• Open devtools networks,
• Click Pet Owner -> New Requet

Expected Behaviour: calls api with user email
Actual behaviour: calls api with undefined

My guess is the user in api.ts won't call the getUser() again, unless upon page refresh.

• Update specializes in pet categories
• set personal daily ratings

• set up schedule tracking for full-time and part-time
• setup constraints for full-time (2 consecutive 150 days of work)

➜  ~ docker image ls
REPOSITORY          TAG                 IMAGE ID            CREATED              SIZE
cs2102_app          dev                 e3c59a8fb994        About a minute ago   301MB
cs2102_app          prod                508a3e9dddf0        7 minutes ago        613MB
<none>              <none>              79fde778cc09        12 minutes ago       301MB
<none>              <none>              1b42cd7fbf8e        14 minutes ago       301MB
<none>              <none>              a6d2eb30ea6f        17 minutes ago       251MB

Currently need to periodically run docker image prune to remove these images and free up spaces. Need a better way to remove these images.

• Index all orders made by pet owner
• Make bid for care taker
• Leave review for care taker

Landing Page

• Inline login on taskbar
• Link to sign up
• Replace favicon with Logo

Sign up Page

• Improve Styling
• Require valid url for gravatar url
• Separate component between Login and SignUp

Dashboard Page

• Blank page
• Link to logout that clears the session

CI pipeline should recreate all tables and reseed the database, upon creating new review apps or staging deployments.

Allow new user to register as pet owner and add pets

Does the ER diagram directly translates to the table?

Pets and Pet Owners

• Pets can have the same name, so we need a id field
  • However, since pets must be owned by a pet owner, there is no point for a pets table and we can add pets to a owner relationship. -> This means that there is no primary key in the pets entity. How do we show this?
  • If its ID dependency, do we still need primary key?

Bids

• Transaction + credit card + bid: is it
  • a paid for relationship connected to credit card, transaction, bid; or,
  • an aggregation between credit card + transaction, and connected to bid

Leaves

• Leave is an entity that contains start date and end date during which a full timer cannot work.
  • What is an atomic leave
• Availability is an entity that contains the start date and end date during which a part timer can work
  • What is an atomic availability

Backend: expose endpoint GET /api/logout that clears req.user.session

frontend: axios get req to '/api/logout', redirecting to landing page '/' on success

• Endpoints like updating pet category should require verifying that user is admin

For a change in pet Category, update all pets that are in that category

https://github.com/thisisadiyoga/cs2102_ay1819_s2

The Prof provided an example project with working business logic. It's written in JS, we need to port some code over to our TypeScript express repository.

1. caretaker most jobs per month (maybe fulltime/parttime split)
2. caretaker that earned the most in the month (maybe fulltime/parttime split)
3. best caretaker per pet category according to rating to price ratio (but price changes? maybe average pet day price throughout month according to bids)

We need either role attribute in Person table or an Admin table.

Blocker for #23 and #31.

As per project requirements, there needs to be at least 1000 users.

• Split into specialized tables for FT and CT
• create view specializes_in, similar to caretaker
• Return CareTaker now with array of SpecializesIn
• Add array of SpecializesIn in req.body of creating and updating caretakers

As a pet owner, I would like to be able to search for pet sitters that are specialized for each of my pets

General idea:

Backend:
Given a selected pet (email, petname pair)

• -> search for part time care takers
• -> search for full time care takers
  Frontend
• -> call both endpoints
• aggregate in frontend, allow for filter between full time or part time

Enforce stricter validation on price field.
sample implementation

Updating pet category creates new pet category

PCS Administrator must be able to update the base daily price for each pet type

Docker is unable to start service db if postgres daemon has already started in userland as port 5432 would already be in use.

Show empty page for CareTaker if user is not a careTaker.

• Create care taker registration flow

• DB: create the pet and pet_category tables as per the ER diagram
• Exposes relative server API, and create adequate client pages
• At the moment, we can hard code the pet_category table?
  • ideally, this is done by the admin

Implementation detail to manag Pet Owner and Care Taker relationship in sign up flow and database representation.
Overall UI design?

Things we can do now:

CRUD for:

• pets
• bids
• credit card details

TBC

After backend is complete,
set up corresponding token verifiers for route groups

#26

POST api/signin should return:

username,
email,
bearer token,
user role (pet owner, care taker, admin)

These information is then persisted in the client's localStorage. The bearer token will be attached to the header of every subsequent request from the client to the server. This will help server to detect if the logged-in user has the permission to perform the requests.

The client will also use the user role field to determine which pages are shown to the user.

Display cards of Pets.

• Support all CRUD operations.
• Allow creating new pet care request from this page directly
  • redirect to new request page with all pet detail prefilled.

Check that a bid can only be made for a caretaker based on these criteria

• Full timer has < 5 active bids in the time period of the new bid
• Part timer has < 5 active bids in the time period of the new bid if he has a rating >= 4
• Part timer has < 2 active bids in the time period of the new bid if he has a rating < 4

This is where DB query gets interesting; can fulfill the interesting query criteria. We can probably display

• The caretaker who took care of the most pets in the past month
• Total transaction amount in the past month
• Total number of pets/caretakers, etc

Full Timer

• 2 * 150 consecutive work days
• cannot apply for leave if bid has been made on those days already
• No overlapping of schedules

A form for pet owners to initiate new Requests. Needs #34

• update userschema in master (latest in dev)
• change SignUpRequest definition to include address, phone, etc
• define error response schema for Login and Signup
• #14

We need a user interface for logged-in users. It can have a tabbed structure, so that each tab is a standalone Component, then we have split the work better.

It could look something like this: https://ant.design/components/layout/#components-layout-demo-top-side-2

• DB: create a credit_card table as per the ER diagram
• Server: expose api/payment/credit_cards CRUD endpoint,
  • Needs to be authenticated, and each user can only modify their own credit card information
• Client: create /profile/payment page that handles CRUD operations that, ideally:
  • Displays a list of current credit cards; a placeholder if none

• Check for confirmed bids and ensure no overlap before allowing insertion of leave / removal of part time schedule

BCrypt hashsync is an expensive operation, which is not neccessary if seed settings are not modified.
Find a way to cache this.

Bug Description:

After encountering an error, frontend is unable to connect to the backend again.
Debugger shows:

Paused on Exception: 
TypeError: i.default.detectStore(...) is undefined

Steps to reproduce:

1. From any page, attempt to access invalid url. eg localhost:3000/foo
2. Return to valid url

Webpage will not be functional as script is paused by debugger.
Resuming then refreshing the page will not resolve the error.

Full Time

• Calculate full time fixed salary of 3000 for first 60 days taking care of any pet (overlaps of many pets on same day count as a sum)
• FT gets 80% of any additional pet days as bonus/commission

Part Time

• gets 75% of any earnings

Endpoints

• Provide get endpoints for fulltimer and parttimer

• end points for creating category, updating price also

Upcoming

• Care taker should see all confirmed, upcoming jobs in the dashboard
• See daily base price (set by admin)

Only return caretakers that fit these additional criteria

• Full timer has < 5 active bids in the time period of the search
• Part timer has < 5 active bids in the time period of the search if he has a rating >= 4
• Part timer has < 52active bids in the time period of the search if he has a rating < 4

Suggested to add a new query and subtract these caretakers from those returned by search_caretaker.

@dingyuchen suggested that it would be nice to have a live preview deployed for every PR. This can be achieve by https://devcenter.heroku.com/articles/github-integration-review-apps#review-apps-and-docker

In the Past Orders page for pet owners, display a list of upcoming orders with the current status, and buttons for the next step.

Current status is one of confirmed, paid, reviewed. The corresponding next step for the statuses are Pay(by credit card), Review.

• Endpoints for sending feedback and review per BID
• identified by PK of BID

Should essentially be another update endpoint similar to setting bid status, but now we update these values