• working api with mongodb
• repo
• app will be on vercel by tomorrow
• I converted the backend to native mongodb instead of mongoose since your calls weren't async and would crash the rendering of the page (like during a search)
  • most of the methods are the same name though
  • also I provided a very documented class to wrap the mongodb connections, you'll find it pretty easy to use.
• Also if you notice the new api keys in the config dir, I think you'll be impressed with the feature I'm adding.
• if you click the working api link: https://golf-handicap-api-ts.herokuapp.com/ with the blank endpoint, a page displaying 'hit' means that the server is running healthy.

PROJECT BOARD

1. hella apis
2. Define what frameworks are being used so we can begin generating a startup script
3. figma links:
   • invite link
   • project link
4. Define schemas and template for json responses (example of json template and schemas)

{
    "status": "success",
    "respone code": "201",
    {
        "key": [
            {"schema for a course"},
            {"schema for a course"},
            {"schema for a course"},
            {"schema for a course"}
        ]
    }
}

Heres how a basic component architecture should look.

function Searchpage({}: Props) {
    const [results, setResults] = useState([] as GolfCourse[]);

    useEffect(() => {
       // some type of loading animation, because this will be called
       // any time searchFunciton is called to change the result list
    }, [results])

    const searchFunction = async () => {
        try {
            const results: GolfCourse[] = await backendCall();
            setResults(results);
        } catch (e) {
            // backend call error
        }
    }

    return (
        <SearchBar source={...} onPress={searchFunction} />
        <SearchResults results={results} />
    );

}

localhost:1337/api/{route}

users/

add - body should contain json consisting of {username: " ", password: " ", token: " "}

get/all - return all the users in the database\

get/by/username/{username} - returns the document for the passed in username

delete/user/{username} - deletes the account associated with the username

change/password/{username}/{new password} - changes the password (will be implemented at a later date)

courses/

post - body should contain json of the course information

get - return all of the courses

get/by/coursename/{course name} - returns the document for specified course

get/par/{course name}/{gender (M or F)}/{color} - return the par based on input

get/course/rating/18/{course name}/{gender (M or F)}/{color} - return the course rating based on input

<<<<<<< HEAD

• finish RESTful API for the users
• make RESTful API for golf courses =======

backend

• Make port branch
• LMK what apis you add to backend
• Link figma

• Add filter to searchbar and implement results components
• Finish Log-In API using rn-async storage
• Fix error with search results using spread operator
• Create union-type of context types for wrapping multiple components
• Research reducer hook
• Decomp Splash Screen to a have animation in external component

• Redux
• Postgres?
• Add Login Api
• Add dropdown

• The Nerdy Canuck:
  • Restful API with NodeJS, Express & Typescript
• Best React Native Documentation
• Old project incase you need it. TS-Movie-List
• Package Search

• relative links are in tsconfig.json
• current thought process is that initial redux check for account login will be in the App.tsx file. (i.e. set the initial page to either the login page or already logged in screen)

• To run server in ./backend yarn serve

• All current heroku config/changes are in the backend branch.
• The name of the current heroku app is handicap-app-711 ---> will change later. was made temp for testing.
• The name of both the project and cluster is handicap. The project name can be changed but the cluster name is immutable.

• The following link will tell you how golf handicaps are caculated. This way you know what we need from our users. tuitorial