MLH-Fellowship / MLH-Fellowship/orientation-project-python-26.SPR.A
Spell check on content added by user
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- 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 by locating the client entry point for user-added Experience, Education, and Skill content and the existing test_pytest.py coverage. Confirm the spelling-check trigger and agree on the response format with the Pod Leader, then add coverage showing the expected before/after results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- full-stack, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100