Group Participators: Nico, Kamila, Elyas and Sebastian Davies
Tech stack:
- Express
- Posgresql
- React
- Javascript
- CSS
Click link here to view the website!
Day 1 Summary - Monday
- No designated leader; decisions made by mutual agreement.
- Document new API routes and link them in the PR.
- Each PR creates or modifies the corresponding file in the docs folder.
- Initial leniency on PRs; priorities will be determined as we progress.
- Focus on working on separate parts of the backend to avoid conflicts.
- Use pair programming if blocked.
- Use Pete’s existing frontend and CSS initially.
- Focus on mobile-first design if time permits.
- Start with regular authentication; OAuth is a backlog item.
- Consider using BCrypt/passportjs for authentication later.
- Not using TypeScript for now.
- Use regular Pool SQL queries instead of a migration library like Knex.
- Decided to use Railway instead of Render.
- Maintain documentation manually with Markdown in the docs folder.
Prioritize authentication tests if time permits. Other tests are a backlog item.
- Implement tags on posts.
- Pagination is low priority and will be considered later.
- Utilize Pete’s frontend and modify if we have time.
- Create news articles and reports on events in fictional worlds or parallel universes.
- Build APIs for news updates to create a continuous alternate reality game.
- Tests for authentication.
- OAuth implementation.
- Mockable database.
- Database Schema: Initial schema design discussed and drafted.
- GitHub Repository: Set up the repository for the project.
- Trello Board: Created a Trello board to track tasks and progress.
- DB Hosting Decision: Evaluated options for database hosting (Nico’s option, Pete’s DB, - Supabase).
- Express Endpoints: Discussed potential endpoints based on frontend requirements.
- File Structure: Reviewed and planned the project’s file structure.
- Hosting Strategy: Decided to start on localhost and consider hosting later for security reasons.
- Cloudflare Tunnels: Considered for future use.
- Prettier Configuration: Set up Prettier for code formatting.
- Finalize database schema and set up the initial database.
- Start implementing API endpoints.
- Continue documenting progress and decisions.
- Set up basic authentication.
- Plan and begin integrating the frontend with the backend.
Day 2 - Tuesday
## Development Update: Day IIToday we added support for process.env.DATABASE_URL to accommodate different database connections.
Engaged in a collaborative pair programming session, enhancing problem-solving efficiency and code quality:
Nico, elyas --> User Routes
Kamila, Seb --> Article routes
We used Live Server in VS code.
Today's updates enhance the functionality and robustness of our user and article management system. The changes are aimed at improving data integrity, user experience, and the maintainability of the codebase.
Method: GET Endpoint: /users
Method: GET
Endpoint: /users/:username
Method: POST
Endpoint: /users
Method: DELETE
Endpoint: /users/:username
Method: GET
Endpoint: /articles
Description: Fetches all articles including their titles, descriptions, publication dates, and authors.
Method: GET
Endpoint: /articles/:id
Description: Retrieves detailed information for a specific article by ID.
Method: POST
Endpoint: /articles
Description: Allows creation of a new article with associated tags. Handles tag existence check and insertion if not present.
Method: DELETE
Endpoint: /articles/:id
Description: Deletes an article and its associated tags from the database.
Method: PUT Endpoint: /articles/:id Description: Updates article details and manages tag associations by clearing old tags and adding new ones.
Method: GET
Endpoint: /articles/with-tag/:id
Description: Retrieves articles associated with a specific tag ID.
Method: GET
Endpoint: /articles/:articleId/tags
Description: Fetches tags associated with a given article.
Day 3 - Wednesday
Today, we focused on integrating the frontend with our backend, addressing issues primarily related to authentication and state management in React/Redux.
- Nico: Worked on authentication.
- Seb, Kamila, and Elyas: Developed Redux slices for various components and functionalities.
- Initiated frontend development.
- Faced issues with authentication.
- Nico focused on resolving authentication problems while the rest of the team worked on Redux slices.
- Encountered significant challenges and felt somewhat directionless.
- Sought assistance from Pete, our senior engineer, for guidance and clarity.
- Made considerable progress in connecting the frontend and backend.
- Successfully displayed some information on the frontend.
- Updated backend endpoints to send data in the format expected by the client.
-
Frontend-Backend Integration:
- Spent a substantial amount of time understanding and working with complex React/Redux code.
- Ensured proper connection and data flow between frontend and backend components.
-
Authorization Fixes:
- Addressed and resolved issues related to user authentication.
- Ensured secure and smooth user login and session management.
Today's efforts were primarily aimed at bridging the gap between our frontend and backend systems, focusing on authentication and data synchronization. Despite facing hurdles and needing additional support, we made significant strides towards a cohesive and functional application.
Overall, these updates enhance the application's user experience and pave the way for smoother development in the following days.
