Update parser grammar to match RFC3501 and RFC4466
Open
Nobody has claimed this yet.
IMAP4rev1
IMAP4rev2
- Dominant language
- Ruby
- Stars
- 118
- Forks
- 43
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 26
Description
- parse most responses in the wild, generally correctly 🙂
- #6
ATOM-CHARvsASTRING-CHAR - #6 CAPABILITY from response code
- #8
resp-textmay begin with "[" or "=""]" - #9 add
BADCHARSETresponse code (Errata Exist) - Complete IMAP4rev1 ABNF (Errata Exist)
- #35
- #113
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 by locating the parser grammar and comparing its remaining unchecked work with the RFC3501 errata and RFC4466 requirements linked in the issue. Done means the IMAP4rev1 ABNF is complete and the parser handles the specified grammar cases; the issue names no particular files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100