Object Destructuring
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- content
Research direction
Open the linked coursework in Sprint-1/destructuring and read the exercise instructions before starting. Work through the object-destructuring exercises on the feature/destructuring branch, following the required commit and pull-request process. Done means the coursework demonstrates extracting object values and assigning them to variables in one line.
Written by the indexing model from the issue text.
Description
Learning Objectives
- Use object destructuring to extract values from an object and assign them to variables in one line
Link to the coursework
https://github.com/CodeYourFuture/Module-Data-Flows/tree/main/Sprint-1/destructuring
Why are we doing this?
Destructuring is very useful and used a lot in React. Both array and object destructuring are worth exploring.
Maximum time in hours
1
Submission & Review
- Fork to your Github account.
- Make a branch for this project called feature/destructuring
- 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.
gitGraph
commit id: "start"
branch feature/destructuring
commit id: "ex-1-update-argument"
commit id: "ex-2-teachers-pet"
commit id: "ex-3-print-receipt"
checkout main
merge feature/destructuring
There are several projects in this repo. Make a new branch for each project. This might feel challenging at first, so this is a good problem to bring to class to work on in groups with mentors.
Don't make one giant PR with all your work in for the module. Make a separate PR for each assignment.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 276
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Data-Flows
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Data-Flows Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Flows Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 3 Core Module-Data-Flows Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Flows Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 1 Core Module-Data-Flows Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Data-Flows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100