yarn add --dev jest babel-jest @babel/preset-env @babel/core @babel/plugin-syntax-jsx @babel/preset-react @testing-library/dom @testing-library/jest-dom @testing-library/react @testing-library/user-event babel-preset-react-app identity-obj-proxy jest-circus jest-scss-transform jest-watch-typeahead
"jest": {
"roots": [
| import { firestorePlugin } from 'vuefire' | |
| import { firebase } from '@firebase/app' | |
| import 'firebase/firestore' | |
| import 'firebase/auth' | |
| import firebaseConfig from '../../firebaseConfig' | |
| let firebaseApp = firebase.initializeApp(firebaseConfig) | |
| let firebaseAuth = firebaseApp.auth() | |
| const db = firebaseApp.firestore() |
PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.
Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories
Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.