Use response content-type to drive initial parser choice
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
If content-type is text/html, try mf2py before feedparser
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-selection entry point and inspect how the response content type is currently handled. Verify the behavior for text/html responses and confirm that mf2py is tried before feedparser, using the project's existing tests or test conventions if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100