Skip to content

Commit cf622ec

Browse files
committed
Solved task Sprint-3/2-practice-tdd/count.js and test cases
0 parents  commit cf622ec

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

61 files changed

+1530
-0
lines changed

.github/FUNDING.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
github: CodeYourFuture
2+
custom: https://codeyourfuture.io/donate

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
blank_issues_enabled: true
2+
contact_links:
3+
- name: CYF
4+
5+
about: Please report serious issues here.
6+
- name: Join CYF
7+
url: https://codeyourfuture.io/volunteers/
8+
about: Join CYF here
9+
- name: CYF Slack
10+
url: codeyourfuture.slack.com
11+
about: Come to #cyf-curriculum and chat
12+
- name: CYF Tech Ed
13+
url: https://github.com/orgs/CodeYourFuture/teams/mentors
14+
about: CYF mentors on Github
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
name: PD Coursework
2+
description: Assign a piece of PD coursework
3+
title: "[PD] <title>"
4+
labels: [PD, 🏝 Priority Stretch, 🐇 Size Small, 📅 Sprint 1]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thanks for taking the time to assign this coursework!
10+
- type: input
11+
attributes:
12+
label: Coursework content
13+
validations:
14+
required: true
15+
- type: input
16+
attributes:
17+
label: Estimated time in hours
18+
description: (PD has max 4 per week total)
19+
validations:
20+
required: true
21+
- type: textarea
22+
attributes:
23+
label: What is the purpose of this assignment?
24+
description: Clearly explain the purpose of this assignment and how trainees can evaluate this.
25+
validations:
26+
required: true
27+
- type: textarea
28+
attributes:
29+
label: How to submit
30+
description: State in clear steps how a trainee can submit this assignment.
31+
placeholder: |
32+
Copy the Google doc to your own Google Drive
33+
Complete the work assigned
34+
When you are ready, move your document to your class Drive
35+
validations:
36+
required: true
37+
- type: textarea
38+
attributes:
39+
label: Anything else?
40+
description: |
41+
Links? References? Anything that will give more context
42+
43+
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
44+
- type: markdown
45+
attributes:
46+
value: |
47+
**Thank you so much.**
48+
49+
Please now complete this ticket by filling in the options on the sidebar.
50+
51+
1. Update labels
52+
- priority -- is this coursework key, mandatory, or stretch?
53+
- size -- help trainees plan their time with rough estimation
54+
2. Add to project backlog
55+
- add to the project named the same as this repo
56+
- fill in custom fields -- priority, size, hours, week -- to match this issue
57+
58+
Once your ticket is complete, you may like to check it out on the example project board attached to this repo.
59+
This is so you understand how trainees will use your work.
Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
name: Tech Ed Coursework
2+
description: Assign a piece of technical coursework
3+
title: "<title>"
4+
labels: [Tech Ed, 🏕 Priority Mandatory, 🐂 Size Medium, 📅 Sprint 1]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thanks for taking the time to assign this coursework!
10+
11+
To support our trainees with planning and prioritising their own learning journey, we want our coursework assignments to be more informative.
12+
We don't just want to tell them what to do, we want to tell them stuff like:
13+
- why we are doing it
14+
- what it's "for" (problem-solving, debugging, etc)
15+
- how long they should spend on it, maximum
16+
- how to get help
17+
- how to review it with answers
18+
- how to get it reviewed from mentors and peers
19+
- type: input
20+
attributes:
21+
label: Link to the coursework
22+
validations:
23+
required: true
24+
- type : textarea
25+
attributes:
26+
label: Learning Objectives
27+
description: https://common.codeyourfuture.io/common-theme/shortcodes/objectives/
28+
placeholder: |
29+
<!--{{<objectives}}-->
30+
- [ ] CYF format, task list formatting
31+
<!--{{</objectives}}-->
32+
- type: textarea
33+
attributes:
34+
label: Why are we doing this?
35+
description: Clearly explain the purpose of this assignment
36+
validations:
37+
required: true
38+
- type: input
39+
attributes:
40+
label: Maximum time in hours
41+
description: (Tech has max 16 per week total)
42+
validations:
43+
required: true
44+
- type: textarea
45+
attributes:
46+
label: How to get help
47+
description: State simply how trainees can get help with this assignment
48+
value: |
49+
Share your blockers in your class channel
50+
https://curriculum.codeyourfuture.io/guides/getting-help/asking-questions/
51+
- type: textarea
52+
attributes:
53+
label: How to submit
54+
description: State in clear steps how a trainee can submit this assignment.
55+
value: |
56+
Fork the repo to your own GitHub account
57+
Make regular small commits with clear messages
58+
When you are ready, open a Pull Request to the CYF repo
59+
Make sure you fill in the PR template provided
60+
validations:
61+
required: true
62+
- type: textarea
63+
attributes:
64+
label: How to review
65+
description: How to get code review and how to self-review
66+
- type: textarea
67+
attributes:
68+
label: Anything else?
69+
description: |
70+
Links? References? Anything that will give more context
71+
72+
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
73+
- type: markdown
74+
attributes:
75+
value: |
76+
**Thank you so much.**
77+
78+
Please now complete this ticket by filling in the options on the sidebar.
79+
80+
1. Update labels
81+
- priority -- is this coursework key, mandatory, or stretch? Pick one.
82+
- size -- help trainees plan their time with rough estimation. Pick one
83+
- topics -- add all that seem relevant to you.
84+
2. Add a Sprint label to add to the backlog view
85+
- sprint 1,2,3,4
86+
87+
Once your ticket is complete, you may like to add it to the example project board attached to this repo.
88+
This is so you understand how trainees will use your work. Nobody has built a board copier yet, so trainees will be doing this step themselves.

.github/pull_request_template.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<!--
2+
3+
You must title your PR like this:
4+
5+
Region | Cohort | FirstName LastName | Sprint | Assignment Title
6+
7+
For example,
8+
9+
London | 25-ITP-May | Carol Owen | Sprint 1 | Alarm Clock
10+
11+
Fill in the template below - remove any sections that don't apply.
12+
13+
Complete the self checklist - replace each empty box in the checklist [ ] with a [x].
14+
15+
Add the label "Needs Review" and you will get review.
16+
17+
Respond to volunteer reviews until the volunteer marks it as "Complete".
18+
19+
-->
20+
21+
## Learners, PR Template
22+
23+
Self checklist
24+
25+
- [ ] I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
26+
- [ ] My changes meet the requirements of the task
27+
- [ ] I have tested my changes
28+
- [ ] My changes follow the [style guide](https://curriculum.codeyourfuture.io/guides/reviewing/style-guide/)
29+
30+
## Changelist
31+
32+
Briefly explain your PR.
33+
34+
## Questions
35+
36+
Ask any questions you have for your reviewer.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
name: Validate PR Metadata
2+
on:
3+
pull_request_target:
4+
types:
5+
- labeled
6+
- unlabeled
7+
- opened
8+
- edited
9+
- reopened
10+
11+
jobs:
12+
validate_pr_metadata:
13+
runs-on: ubuntu-latest
14+
steps:
15+
- uses: actions/checkout@v4
16+
- uses: CodeYourFuture/actions/validate-pr-metadata@main
17+
with:
18+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
node_modules
2+
.DS_Store
3+
.vscode
4+
**/.DS_Store

.prettierrc

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
{
2+
"arrowParens": "always",
3+
"bracketSpacing": true,
4+
"embeddedLanguageFormatting": "auto",
5+
"htmlWhitespaceSensitivity": "css",
6+
"insertPragma": false,
7+
"jsxBracketSameLine": false,
8+
"jsxSingleQuote": false,
9+
"printWidth": 80,
10+
"proseWrap": "preserve",
11+
"quoteProps": "as-needed",
12+
"requirePragma": false,
13+
"semi": true,
14+
"singleQuote": false,
15+
"tabWidth": 2,
16+
"trailingComma": "es5",
17+
"useTabs": false,
18+
"vueIndentScriptAndStyle": false
19+
}

.vscode/extensions.json

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
{
2+
"recommendations": [
3+
"esbenp.prettier-vscode",
4+
"dbaeumer.vscode-eslint",
5+
"streetsidesoftware.code-spell-checker",
6+
"eamodio.gitlens",
7+
"ritwickdey.LiveServer",
8+
"vsliveshare.vsliveshare",
9+
"Orta.vscode-jest"
10+
]
11+
}
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
let count = 0;
2+
3+
count = count + 1;
4+
5+
// Line 1 is a variable declaration, creating the count variable with an initial value of 0
6+
// Describe what line 3 is doing, in particular focus on what = is doing

0 commit comments

Comments
 (0)