We were able to complete the base functionality of the back-end application. The front-end application has functionality including adding and deleting to the database without pageload. The application's FE does not integrate PATCH functionality on the DOM, however, the endpoints are fully set-up and capable.
- N/A
- Why were you proud of this piece of code?
Our team is thrilled to have created a functioning backend, and more specifically, a dynamic function that gives a front-end developer using our API what they need to maneuver the app. We were able to think through the needs of the developer and expose an API endpoint that returns the palettes of a specififed folder based on the folder ID. Our source of pride on this piece of code comes from piecing together what we learned in class and reaching outside of that to create a truly useful endpoint.
- Why do you feel not awesome about the code? What challenges did you face trying to write/refactor it?
There are lots of things to be proud of in this project. Our team worked together well, communicated effectively, and implemented a working application. Unfortunately, we were unable to utilize all of our API endpoints. Eventually, our team had to make a strategic decision on how best to allocate time. We were happy with creating the backend patch requests, apiCalls asyncronous functions, and app-level implementation, but were unable to connect it on the DOM-level. These projects require priotitization and this is one of those instances. We've created a set of issues in GitHub for this reason.
- Our project design inspiration - Besides the obvious inspiration of Mr. Bob Ross, our team also drew inspiration from the attached project comp that utilizes transparency over imagery. We utilized this feature in our project.
- Describe your thoughts on server-side testing
Server side testing was a pleasure. The syntax of the testing is friendly and you are able to easily query the database directly to create "mock data" and then utilize those results to create expectations. It was great to be able to easily test both happy and sad paths.
- Describe your thoughts on TravisCI -
TravisCI seems like a very useful tool. It is great to have a failsafe in place to run your test suite prior to deployment. Thank you for this lesson.
- Describe your thoughts in creating a single project whose codebase was distributed across multiple repositories -
The project was very interesting in terms of connecting the BE and FE repositories. It was particularly interesting to be in charge of the way that data is served up to the front end. The project gave a great full-picture view of application development. It was nice to have two repositories and clear responsibilities between each.
Anything else you wanna say!
x score:
x score:
x score:
x score: