gjtorikian / gjtorikian/markdowntutorial.com
Response processing
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 606
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
When you go to the next step without even having passed the previous step, it's congratulations anyway. It would be nice to put in place an algorithm that allows you to check whether or not you have passed the test. It will also give a playful aspect.
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.
Research direction
No files, tests, or entry points are named. Start by tracing how the tutorial advances between steps and how responses are processed, then define the pass condition and verify that advancing is blocked until the previous test is passed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100