Codewars API Project
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start with the linked Codewars-API-Project coursework repository and review its README or starter files. Complete the listed objectives: fetch Codewars data, adapt and extend a web component, and create a new component to display more data. Done means the coursework is working and a pull request is opened against the CYF repository using its template.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://github.com/CodeYourFuture/Codewars-API-Project
Learning Objectives
- Explain how components are used in web development
- Adapt an existing web component to show your own data
- Extend this web component to present more data from the Codewars API
- Create a new web component that presents data from the Codewars API
Why are we doing this?
Let's play with grabbing some data from an API and displaying it on a website. We will be using the the Fetch API to make requests to the Codewars API and the Web Components API to display the data we get back.
Maximum time in hours
0
How to get help
General advice on asking for help can be found on the curriculum pages.
You can always share your blockers in your class channel and get help from your colleagues.
Your mentors track trainees' progress through the set katas in a very similar way - why not ask them for advice?
Submission & Review
Fork the coursework repo to your own GitHub account.
Make regular small commits with clear messages.
When you are ready, open a Pull Request to the CYF repo. Make sure you fill in the PR template provided.
A volunteer will review your submission and send you feedback.
- 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
-
bug customer-eng Durable Agents Inngest status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-cao#13475 ·
-
[BUG]: "Clear All" in Settings doesn't clear the saved analysis, old data comes back after reload Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
AOSSIE-Org/OrgExplorer#253 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
oxc-project/oxc#26944 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100