n-gibson / back-end-palette-picker

---

Hi there, I'm Noah 👋

I am a full stack developer with experience in JavaScript, React.js, Node.js and more! As a tech enthusiast, my journey began early in life as a timkerer of toys, tools and electronics. This childhood passion grew and evolved into a job in construction then IT ans software development. Attention to detail is a core value of mine when building anything from a React app to a retaining wall. My passions exist in the natural world and I hope to use the tech platform to help preserve the natural beauty around us. Through tech and tinkering we can make the world a better place!

---

📫 Reach me on:

• LinkedIn
• Resume
• Email

---

About Me

• 🔭 I’m currently working on an app for Timberline Incorperated, revamping design and functionality.
• 👯 I’m open to collaboration.
• 💬 Ask me about anything outdoor related, it's my favorite hobby!
• Currently open for work, reach out with any questions.

---

Stats

back-end-palette-picker's Issues

PATCH palette name

PATCH:

• As a user I should be able to PATCH to api/v1/palettes/:id to edit an existing palette name
• write PATCH for endpoint /api/v1/palettes/:id
• Body should contain: Name
• test PATCH in postman

GET single project

GET:
As a user I should be able to visit /api/v1/projects/:id to see a specific project based on its id

• write GET for endpoint /api/v1/projects/:id
• test GET in postman

TEST for getting all palettes

TEST:

• Write all tests for GET /api/v1/palettes
• include test for 'should return 200 status for successful GET'
• include test for 'should return 404 status for unsuccessful GET'

POST palette

POST:

• As a user I should be able to POST to api/v1/projects to create a new project
• write POST for endpoint /api/v1/projects
• Body should contain: Name, color1, color2, color3, color4, color5
• test POST in postman

POST project

POST:
As a user I should be able to POST to api/v1/projects to create a new project

• write POST for endpoint /api/v1/projects

• Body should contain: Name

• test POST in postman

TEST for getting single project

TEST:

• Write all tests for GET /api/v1/projects/:id
• include test for 'should return 200 status for successful GET'
• include test for 'should return 404 status for unsuccessful GET'

DELETE project

DELETE:

• As a user I should be able to DELETE to api/v1/projects/:id to remove an existing project
• write DELETE for endpoint /api/v1/projects/:id
• test DELETE in postman

PATCH project name

PATCH:

• As a user I should be able to PATCH to api/v1/projects/:id to edit an existing project
• write PATCH for endpoint /api/v1/projects:id
• Body should contain: Name
• test PATCH in postman

DELETE palette

DELETE:

• As a user I should be able to DELETE to api/v1/palettes/:id to remove an existing palette
• write DELETE for endpoint /api/v1/palettes/:id
• test DELETE in postman

TEST for getting single palette

TEST:

• Write all tests for GET /api/v1/palettes/:id
• include test for 'should return 200 status for successful GET'
• include test for 'should return 404 status for unsuccessful GET'

TEST for getting all projects

TEST:

• Write all tests for GET /api/v1/projects
• include test for 'should return 200 status for successful GET'
• include test for 'should return 404 status for unsuccessful GET'

Add custom query param

Need to add in a custom endpoint for getting specific color

GET all pallets

GET:
As a user I should be able to visit /api/v1/palettes to see all palettes

• write GET for endpoint /api/v1/palettes
• test GET in postman

GET all projects

GET:
As a user I should be able to visit /api/v1/projects to see all projects

• write GET for endpoint /api/v1/projects
• test GET in postman

Change logic to backend

Switch logic with deleting project (and therefore palettes) from the front end to the backend endpoint.

GET single palette

GET:
As a user I should be able to visit /api/v1/palettes/:id to see a specific pallet based on its id

• write GET for endpoint /api/v1/palettes/:id
• test GET in postman