π backlog
Module-Node π
London 10 | Abubakar-Meigag | NodeJS | chat-server-project π
Your Details
Your Name: Abubakar Meigag
Your City: London
Your Slack Name: Beko Meigag
Homework Details
Module: Node JS
Week: 2
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
London10-Anna_Hrychaniuk-Module_Node-week_2 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
GLA6 | Mandy Cheung | Node | Week 2 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Glasgow class - 6 | Herish Turki | Module-Node-Chat server api project π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Glasgow class 6 | Rahma Berhan | Node - Quote Server | week 1 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
London 10 | Seyyednavid hejazijouybari | NodeJS_week2 | Mailing-List-API π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Glasgow 6 | Delnia Alipour | Module-Node | Chat-Server π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
London 10 | Seyyednavid hejazijouybari | NodeJS_week2 | Hotel-booking-API π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Glasgow 06 - Malkit Benning - Node chat server - Week 2 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
London 10 | Seyyednavid hejazijouybari | NodeJS_week2 | Chat server π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Glasgow class - 6 | Herish Turki | Module-Node-Mailing-List-API π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
- Added error handling for the case where the name in the URL path doesn’t match the one in the JSON body of the request in the PUT method of the mailing list API.
Questions
Ask any questions you have for your reviewer.
No questions at the moment.
GLASGOW Class _ 6 | Herish Turki | Module-Node _ Quote_server π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Bump tough-cookie from 4.1.2 to 4.1.3 π
Bumps tough-cookie from 4.1.2 to 4.1.3.
Release notes
Sourced from tough-cookie's releases.
4.1.3
Security fix for Prototype Pollution discovery in #282. This is a minor release, although output from the
inspect
utility is affected by this change, we felt this change was important enough to be pushed into the next patch.
Commits
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
- dependencies
[TECH ED] ποΈ Stretch challenges π
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/tree/main/hotel-bookings-api
Why are we doing this?
These tasks will get you to further develop your skills by implementing more functionality for your server projects.
Check out the tasks underneath the π Stretch challenges heading in the README.
Maximum time in hours
2
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
Follow the instructions on the linked repo
- ποΈ Priority Stretch
- π Size Medium
- π Node
[PD] Reflect about your own biases π
Coursework content
Think of the times when you are stressed, feeling tired, or rushed, as these situations tend to activate our biases. How may these feelings influence your behaviour when working in a team? Reflect in a 250-word essay.
Additionally, fill in the blanks in the following template and share in your cohort’s channel: “Once when I was […], someone […]. I caught myself thinking […]. Then I […].”
An example: “Once when I was late for an exam, someone was driving very slowly in front me. I caught myself thinking that they are driving slowly on purpose to slow me down. Then I realised that they don’t know me and I don’t know their situation. I decided to find a polite and kind way of passing them through.”
Estimated time in hours
1
What is the purpose of this assignment?
This assignment will help you recognise the situations that require an extra effort to overcome biases.
How to submit
Share the link for the Google doc you prepared on your own coursework project board.
Share your answer to the template in your cohort’s channel.
- π Priority Mandatory
- π Size Small
- π Priority Key
- π Node
- Week 2
[PD] Challenge yourself π
Coursework content
Take an Implicit Association Test (IAT) (link is here) to identify what your unconscious biases are. There are multiple topics to choose from: Age, Gender, Sexuality, Skin-tone, Ethnicity, etc. Remember: Awareness is the first step to combatting bias.
Estimated time in hours
0.2
What is the purpose of this assignment?
This assignment will help to recognise your own biases that maybe you were not aware of.
How to submit
Complete the test. You don’t need to share the results.
- π Size Small
- π Node
- Week 2
[PD] Brag Diary π
Coursework content
Write your first entry for your Brag Diary.
This will be the record of your achievements, the moments you feel proud about yourself. Think positively, you might find more to write than you think. Take turns to present your diary entries in your group meetings with your PD buddy or your study group.
Estimated time in hours
0.5
What is the purpose of this assignment?
This assignment will help you to capture, record, remember, share and celebrate your achievements.
How to submit
Share the link for the Google doc you prepared on your own coursework project board.
- π Priority Mandatory
- π Size Small
- π Node
- Week 1
Solutions π
[TECH ED] Hotel Bookings API π
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/tree/main/hotel-bookings-api
Why are we doing this?
In this challenge you will take all your knowledge of APIs and backend thus far to build an API that can process a full range of different HTTP requests.
Maximum time in hours
12
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
- Fork to your Github account.
- Make a branch for this project.
- Make regular small commits in this branch with clear messages.
- When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
- π Priority Mandatory
- π Size Medium
- π Priority Key
- π Node
[TECH ED] ποΈ Stretch challenges π
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/blob/main/chat-server/README.md
Why are we doing this?
These tasks will get you to further develop your skills by implementing more functionality for your server projects.
Check out the tasks underneath the π Stretch challenges heading in the README.
Maximum time in hours
2
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
Follow the instructions on the linked repo
- ποΈ Priority Stretch
- π Size Medium
- π Node
[TECH ED] Chat Server API Project π
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/tree/main/chat-server
Why are we doing this?
In this project, you’ll be able to start building out different method endpoints that accept POST
requests.
You’ll need to complete up to Level 1 in the Chat server API project.
Maximum time in hours
12
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
- Fork to your Github account.
- Make a branch for this project.
- Make regular small commits in this branch with clear messages.
- When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
There are several projects in this repo. Make a new branch for each project.
- π Priority Mandatory
- π Size Medium
- π Priority Key
- π Node
[TECH ED] ποΈ Stretch challenges π
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/edit/main/quote-server/README.md
Why are we doing this?
These tasks will get you to further develop your skills by implementing more functionality for your server projects.
You can find the stretch section in the README under the π Stretch challenge heading.
Maximum time in hours
2
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
Follow the instructions on the linked repo
- ποΈ Priority Stretch
- π Size Medium
- π Node
- Week 1
[TECH ED] Codewars π
Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on the CodeYourFuture account.
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
Maximum time in hours (Tech has max 16 per week total)
1
How to get help
- Join the #cyf-codewars Slack channel
- Read the CYF Codewars docs
- Read Codewars advice from CYFers
- Read Codewars advice from mentors
Remember, after 20 minutes, take a break.
How to submit
Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.
How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
- π― Topic Code Review
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π― Topic Requirements
- π― Topic Time Management
- π Priority Mandatory
- π Node
[TECH ED] Codewars π
Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on the CodeYourFuture account.
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
Maximum time in hours (Tech has max 16 per week total)
1
How to get help
- Join the #cyf-codewars Slack channel
- Read the CYF Codewars docs
- Read Codewars advice from CYFers
- Read Codewars advice from mentors
Remember, after 20 minutes, take a break.
How to submit
Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.
How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
- π― Topic Code Review
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π― Topic Requirements
- π― Topic Time Management
- π Priority Mandatory
- π Node
[TECH ED] Codewars π
Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on the CodeYourFuture account.
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
Maximum time in hours (Tech has max 16 per week total)
1
How to get help
- Join the #cyf-codewars Slack channel
- Read the CYF Codewars docs
- Read Codewars advice from CYFers
- Read Codewars advice from mentors
Remember, after 20 minutes, take a break.
How to submit
Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.
How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
- π― Topic Code Review
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π― Topic Requirements
- π― Topic Time Management
- π Priority Mandatory
- π Node
[TECH ED] Codewars π
Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on the CodeYourFuture account.
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
Maximum time in hours (Tech has max 16 per week total)
1
How to get help
- Join the #cyf-codewars Slack channel
- Read the CYF Codewars docs
- Read Codewars advice from CYFers
- Read Codewars advice from mentors
Remember, after 20 minutes, take a break.
How to submit
Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.
How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
- π― Topic Code Review
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π― Topic Requirements
- π― Topic Time Management
- π Priority Mandatory
- π Node
[TECH ED] Call an API π
Link to the coursework
http://api.tvmaze.com/shows/82/episodes
Why are we doing this?
This task will get you to really think about the response you get back from an API. In addition, it will encourage you to use Chrome Dev Tools to examine the response you get back from a server.
Look at a request in Chrome Dev Tools
In Google Chrome, open dev tools network tab and enter this URL into the browser: http://api.tvmaze.com/shows/82/episodes
Answer the following questions:
What’s the status code the server sent back?
What HTTP method did the browser use to make the request?
What is the request path?
What is the first line of the response body?
What is the value of the response header called “Content-Type” ?
What is the value of the request header called “User-Agent”
Maximum time in hours
2
How to submit
Share your answers with the other trainees in your Buddy Group or on your Slack class channel.
Did you get different answers to other people? Ask them how they worked them out!
- π Priority Mandatory
- π Size Medium
- π Node
- Week 1
[TECH ED] Quote server API Project π
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/edit/main/quote-server/README.md
Why are we doing this?
This assignment is designed to give trainee’s an opportunity to practice building simple GET endpoints using express. It will also provide the opportunity to get used to invoking API endpoints using client applications like Postman.
Maximum time in hours
10
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
- Fork to your Github account.
- Make a branch for this project.
- Make regular small commits in this branch with clear messages.
- When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
There are several projects in this repo. Make a new branch for each project.
How to review
You can request a review for this assignment by adding the label review-requested to this piece of work.
- π Priority Mandatory
- π Size Medium
- π Priority Key
- π Node
[TECH ED] Prepare for live session π
Link to the coursework
Why are we doing this?
It is essential to start learning new concepts and ideas before Saturday’s session. During the week, we expect you to get stuck and form questions about the new content so you can address misconceptions during Saturday’s session. The prep work here will introduce you to the new concepts for the week.
Maximum time in hours (Tech has max 16 per week total)
3
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
- :brain: Prep work
- π Priority Mandatory
- π Size Medium
- π Node
- Week 2
[TECH ED] Prepare for live session π
Link to the coursework
Why are we doing this?
It is essential to start learning new concepts and ideas before Saturday’s session. During the week, we expect you to get stuck and form questions about the new content so you can address misconceptions during Saturday’s session. The prep work here will introduce you to the new concepts for the week.
Maximum time in hours (Tech has max 16 per week total)
3
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
- :brain: Prep work
- π Priority Mandatory
- π Size Medium
- π Node