Miscellaneous Information:

- Automated tests are run on every push to the repo with results mailed to checkyourbias@u.washington.edu

- Issues are tacked through Github's issue tracker

- New releases can be made or examined using Github's release feature

- Check out our development blog

Design Patterns

One of the major design patterns we decided to follow as a team was using the Facade pattern with Firebase. The Facade pattern allows us to make Firebase more readable by including Typescript classes which can be used with the frontend code. For example, we have our user class which provides a simplified and easier to use/understand interface than connecting to Firebase alone and using the data as a JSON object. Other examples can be found in our common folder in our source code.

A second major design pattern that we utilized was the Observer pattern. This pattern occurs when an object, referred to as the subject, keeps a list of other objects (known as observers) that are called when a specific event occurs within the subject. Using Javascript and React, this occurs in almost every module. A great example of this can be found within our crowdsourcing code. In this piece of code, we pass handleCandidateMap and handleContent, which are functions, to a form component. These are then called when a candidate has been updated, which can be found here. This lets the observer (CrowdsourcingSubmitContentComponent) know when a change has occurred in the subject (CrowdsourcingQuoteComponent or CrowdsourcingGeneralComponent).