[docs] lazydocs to mkdocstrings #1060
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
CodSpeed Performance ReportMerging #1060 will not alter performanceComparing Summary
|
| for file in Path(input_dir).rglob("*.md"): | ||
| output_file = file.with_suffix(".mdx").name | ||
| print(f"Processing {file} -> {output_file}") | ||
| parser.process_file(str(file), str(Path(input_dir) / "mintlify" / output_file)) |
There was a problem hiding this comment.
Bug: Missing Directory Causes File Writing Error
The process_files function writes generated MDX files to a mintlify subdirectory within the input_dir. This directory isn't explicitly created, which can cause a FileNotFoundError when the script attempts to write files.
| (output_path / "index.mdx").write_text(readme_text) | ||
| readme_text = Path("README.md").read_text() | ||
| readme_text = header + readme_text | ||
| (output_path / "index.mdx").write_text(readme_text) |
There was a problem hiding this comment.
Bug: Inconsistent File Path Handling
The copy_readme function always writes index.mdx to a hardcoded path, while process_files uses a path derived from the input_dir argument. This inconsistency can lead to index.mdx being placed in a different output directory than other processed files when a custom input directory is used, potentially breaking the documentation build.
This PR migrates from
lazydocstomkdocstrings