This week, I focused on building the backend for my band’s web application. My primary tasks included developing routes, defining schema models, and setting up controllers, all while successfully connecting the application to a MongoDB Atlas database.
Challenges and Solutions
One of the initial hurdles I faced involved troubleshooting naming inconsistencies across exports and imports. Through debugging, I resolved these issues by carefully aligning names in my codebase.
Another significant challenge was connecting the app to the MongoDB database. After some investigation, I discovered that the <PASSWORD> placeholder in my config.env file didn’t match the <password> key referenced in the server.js file. Once corrected, the connection was established successfully.
Progress So Far
With the connection in place, I tested the endpoints using Postman. I started with the merchandise routes, as they were straightforward to validate. I then tested and documented all available endpoints for the Albums, Merch, Shows, Webcasts, and Tracks models.
Current Focus
I am currently implementing advanced API features to enhance functionality, including:
- Sorting
- Filtering
- Advanced filtering
- Field limiting
- Pagination
- Aliasing
Next Steps
Once the API features are complete, I will shift my focus to user authentication. My plan includes creating separate sign-up and login functionality for both fans and band members. Additionally, I will address error handling and begin refactoring my code to adhere to the DRY (Don’t Repeat Yourself) principle, improving maintainability and readability.
This week has been productive, with significant progress made in laying a strong foundation for the application. I’m excited to continue refining and expanding the project in the coming weeks!
Top comments (0)