RFC5258 (2008): `LIST-EXTENDED` (mostly included in `IMAP4rev2`)
Open
Nobody has claimed this yet.
IMAP4rev2
- Dominant language
- Ruby
- Stars
- 118
- Forks
- 43
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 26
Description
RFC5258 also established an IANA registy.
- Add select options to
#list, using RFC4466tagged-extsyntax - Add return options to
#list, using RDC4466tagged-extsyntax - Parse all RFC9051
mbox-list-extended-itemdirectly- TODO: add appropriate tickets here...
- Parse all other
mbox-list-extended-itemextensions directly- TODO: add appropriate tickets here...
- Parse unknown
mbox-list-extendedinto TaggedExtensionData
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 at the #list API and compare its current handling with RFC4466 tagged-ext syntax and RFC9051 mbox-list-extended-item requirements. Implement the listed select and return options, parse known and unknown extensions into TaggedExtensionData, and add the appropriate focused tests for each completed checklist item.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100