microsoft / microsoft/markitdown
Make structure changes.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 186k
- Forks
- 13.7k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
Hello everybody!
Hope you are doing well.
I reviewed the latest version of the _markitdown.py file, and its content is already more than 1.5K. Maybe it's time to leave in _markitdown.py only the class MarkItDown, and move other classes in other modules?
It's just a suggestion.
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 reviewing _markitdown.py and identifying the classes besides MarkItDown that would be affected. The issue does not name target modules, tests, or a concrete module layout, so first establish those boundaries and how existing behavior will be verified. Done means the structure is split without changing the converter's behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100