Courtside Devlog 2: Team Work

Adding Teams

The first part of this process was creating new backend routes to get team data from the database. I created two new routes: /teams which returns all teams in the database, and /teams/<code> which returns the data for a specific team.

Then I created a new screen which displays all team options and lets users select the option they want.

The Team Selection screen

On this screen, when the user hits the Update button, the results are saved to user’s preferences on in device storage and in the database. The next step will be displaying the user’s teams on the Teams Dashboard page.

Adding Team Members

A few of our members have switched onto the frontend stack for this semester since most of our backend is fleshed out and handled by Rylee, Jake, and me.

To help with this transition, I added a few pages to our GitHub wiki about resources that can be used to learn JavaScript and React Native. This includes documentation websites, videos, and reference sites. My hope is that soon all teams members will be fully integrated on the frontend and will be able to create useful and productive code.

Documenting the Backend

On the backend, I wrote the handlers for our authentication system and this week I went back to fully document them. Instead of using JavaDoc like I did for the frontend JavaScript code, I followed Google’s Python Style Docs instead.

@app.route('/team/<code>', methods=['GET'])
def get_team(code):
    """Returns the data for the team with the specified code
    Args:
        code: the team's three letter code as a string
    Returns:
        A Response object with the team's data including its id, name, and team code
    """

For methods, this format has you writing a quick description of a function with its arguments(Args), return value (Returns), and any errors that the function raises (Raises).

For modules, this format has a one line summary of the module, followed by a more in depth explanation of exported classes and functions, and an example of usage.