Donor Page View API + Frontend Add Donor + Donate Functionality

[ysiddhapura]

Donor Feature work in progress

Refer to #193

[parthpandey1]

Created a GET endpoint to fetch all users with at least one donation.
Steps to test:

1. Pull from 'donorlookup' branch.
2. docker-compose up
3. curl http://localhost:3001/donors

Should return a JSON with person_id, full name and email of all donors.

[briswells]

@parthpandey1 Code look awesome, and works correctly. Could you add authentication to the route. Just passing ensureAuthenticated as a route argument does not cause it to require authentication. You can look at the /feed route for an example.

[parthpandey1]

Did the following as part of 1b38344 and 5181aab :

1. Added an endpoint for donor lookup. This endpoint will return persons with at least one donation who match the description (first_name and/or last_name and/or id). Steps to test:

• Pull from 'donorlookup' branch.
• docker-compose up
• Download and install postman.
• Follow the instructions provided by @briswells on discord. After downloading postman create a collection, on the authorization tab under type select bearer token, then set Token to
  {{token}}
  after doing so select the pre-request script tab and paste the following code into it:

pm.sendRequest({
    url: 'localhost:3001/login',
    method: 'POST',
    header: {
        'content-type': 'application/json'
    },
    body: {
        mode: 'raw',
        raw: JSON.stringify({"email":"johndoe@example.com", "password":"password" })
    }
}, (err, res) => pm.collectionVariables.set("token", res.json().token));

and hit save.

After doing so you can click the 3 dots shown when highlighting your collection on the left, click Add Request and input values required for testing.

• Send requests with query parameters like http://localhost:3001/lookupDonor?first_name=John&last_name=Doe or http://localhost:3001/lookupDonor?person_id=1 or http://localhost:3001/lookupDonor?first_name=John&last_name=Doe&person_id=1
• The response JSON should include person details (person_id, first name, last name, and email) which match the search criteria.
  

This completes the 2nd BE task in #193

Note: The first_name and last_name search parameters do not have to be exact (for example if dummy_data.sql is run, http://localhost:3001/lookupDonor?first_name=John and http://localhost:3001/lookupDonor?first_name=Joh will return the same result). However, person_id should be exact to return results.

2. Added authentication to /donors endpoint as suggested by @briswells

[briswells]

Looks great. Sorry I didn't notice this earlier but I would suggest is changing the names of the query parameters to be fname, and lname, just to keep everything consistent. You could also map the return dict so it returns data using the same dict keys that are being used for the API query parameter. Although this may cause confusion as different user routes might return the same fields named different things.

[jayrevolinskyjr]

I've opened this PR for review since it has so much code and checks off 13 out of the 16 original subtasks. The remaining tasks are broken down into #232, #233, #234.

Heads-up to any code reviewers, there was a significant amount of UI edits merged to main that generated conflicts, resolving those conflicts generated code bloat in this branch.

[reembot]

Live review performed with @ysiddhapura -
Reduced feature targets to mitigate PR bloat. New issues have been created for pending funtionality/features.

[jayrevolinskyjr]

Runs like a charm on my machine