Each member of the team gets the code running on their systems by the end of sprint 1

• Archie
• Natalie
• Jeffery
• Ayesha
• Marilena

Merged the old wiki into our new one so we can see what they were planning and what they have documented.

There are at least a few links that need to be updated and some organisation to do.

Everyone creates a simple front end for their individual app

• Archie
• Natalie
• Jeffery
• Ayesha
• Marilena

MVP for sprint 1 - Make a new app on the frontend

Each member of the team creates a separate branch on git for their work on the project

• Ayesha
• Natalie
• Archie
• Jeffrey
• Marilena

• The error messages for incorrect password isn't correctly displayed on wrong email/password.
• on signup page, 'Already have an account' leads to '/login' it should lead to '/signin'.

When we figure this out @marilenaManoli lets make sure we document it in the setup instructions for any future mac or older python users who pick up the project 👍

Seems like this is redundant and the route should just only accept post requests?
Need to check and test before removing though.

If it is an issue it looks like there is a similar thing with /register.

Need to investigate how serious this security flaw is

• We need to add ESLint to the project and fix these to improve code quality
• Once this is done we need to add the linter to our CI/CD / PR pipeline so no more warnings get into main

In react router v6 something like this could become

<Route path="/dipstik" element={<DipstikInstructions />} />
<Route path="/dipstik/dipstik-timer" element={<DipstikTimer />} />
<Route path="/dipstik/dipstik-camera" element={<DipstikCamera />} />
<Route path="/dipstik/dipstik-results" element={<DipstikResults />} />

Something like

<Route path="/dipstik" element={<Outlet/>} />
      <Route path="/" element={<DipstikInstructions />} />
      <Route path="/dipstik-timer" element={<DipstikTimer />} />
      <Route path="/dipstik-camera" element={<DipstikCamera />} />
      <Route path="/dipstik-results" element={<DipstikResults />} />
</route>

for better DRY

https://github.com/Archie-Adams/larks/wiki/Simulating-a-React-page-on-mobile-devices

The last repository did a pretty bad job with repo management.

As a team we should get together and think about:

• Deleting branches after PR's (no confusing hanging branches by the end of it)
• Branch naming conventions
• Code quality and testing checks required for PR pass
• atomic commits
• commit messages

just basic stuff we ought to be on the same page with

In the App.tsx file lines 21-30 'deals' with showing the user a login page when they are not authenticated.

This poor implementation means that the header is now shown always on the signup page, and also means that a user can manually navigate to the loginpage when loggedin, putting the app in an undefined state.

The proper way to deal with this is to define a guarded route component to be used in Routes.tsx for urls only authenticated users can access, which redirects the user to login otherwise.

The frontend is organised so that shared components are in the same directory as the apps.

This doesn't really make sense.

The test suite should destroy their databases so a clean start is ready for the next run.

Can probably wait until this repo gets a wiki

• Data can be send to the frontend
• Data from the frontend can be stored

Need to split out the massive App.css

eg, if the backend is not running or can't be contacted

Shouldn't be too difficult they're a similar format and the current tests on gitlab don't all work and are skipped anyway.

A service like Swagger or JSDoc that could auto document the API routes and return types which could be generated as TS for the frontend?