Switch to using lex and yacc for OO request parsing
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Right now OO request string parsing is done using regular expressions. That's hard to read and maintain. Instead switch to using lex and yacc modules. See kpet's ssp.py module for an example.
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
Start in kcidb/oo/data/init.py around line 276, where OO request strings are parsed with regular expressions. Read kpet's ssp.py example to understand the proposed lex and yacc approach. Done means replacing the regex-based parsing with lex and yacc modules while preserving OO request parsing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100