MLH-Fellowship / MLH-Fellowship/orientation-project-python
Spell check on content added by user
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Be able to check that Experience, Education and Skill do not contain any spelling errors. This should be triggered by the user from the client. The format returned should follow this format:
[
{
"before": "Hellq there",
"after": "Hello there"
}
]
If a better format can be found, this must be discussed with your Pod Leader to make sure the fellows contributing to the JavaScript repository can build functionality to match it.
This should include a test in test_pytest.py to show that it works correctly.
Contributor guide
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
Start with the client-trigger requirement and the existing test_pytest.py test file, then identify where Experience, Education, and Skill content is handled. Done means user-triggered spell checking returns the specified before/after JSON structure and test_pytest.py demonstrates the behavior; discuss any format change with the Pod Leader.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100