feat(core): Add Prettier formatting and markdownlint checks to output + project-wide lint cleanup#31
Merged
samchon merged 3 commits intosamchon:masterfrom May 16, 2025
Merged
Conversation
Contributor
Author
|
why did you rollback ? |
samchon
reviewed
May 15, 2025
samchon
reviewed
May 15, 2025
Owner
samchon
left a comment
There was a problem hiding this comment.
Using prettier is careful, because it sometimes breaks table content.
I changed the code to write markdown content with prettier applied as much as possible.
Owner
|
If you still need prettier to markdown content, please do it manually after generation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces several quality-of-life improvements and linting enhancements for the prisma-markdown project:
✅ Formatted the generated Markdown output using Prettier
Ensures consistent and readable output formatting when generating documentation.
🧪 Added a pre-commit hook configuration (.pre-commit-config.yaml)
Uses markdownlint to validate the generated output during pre-commit to catch issues like broken links or spacing problems early.
🧹 Linted the entire codebase
Cleaned up formatting and consistency issues across the project, including test files.
🔧 Additional Notes:
The Prettier formatting is applied directly at the end of the Markdown generation pipeline.
The pre-commit setup requires pre-commit to be installed locally (pip install pre-commit or brew install pre-commit).