Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: add a verbose (or debug mode) #146

Closed
ccoVeille opened this issue Apr 2, 2024 · 4 comments · Fixed by #150
Closed

Feature request: add a verbose (or debug mode) #146

ccoVeille opened this issue Apr 2, 2024 · 4 comments · Fixed by #150

Comments

@ccoVeille
Copy link
Contributor

It would be interesting to be able to see the formatter that is running on each file

Of course, it would be only something to ask on demand.

maybe like a -v that inform that block from line X to Y is sent to prettier/shfmt.

with a -vv the information would be more details with the block content before calling the method, then after/ but also the exact path of the formatter used.

it could also be a kind of log level info/warn/error/debug

@ccoVeille
Copy link
Contributor Author

right now I used strace -ff mdsf file.md to see what happens under the hood

@hougesen
Copy link
Owner

hougesen commented Apr 2, 2024

Currently the --debug argument enables stdout/stderr of the formatters.

Adding the formatter and line info should be pretty straightforward 😃

hougesen added a commit that referenced this issue Apr 2, 2024
@ccoVeille
Copy link
Contributor Author

Currently the --debug argument enables stdout/stderr of the formatters.

Adding the formatter and line info should be pretty straightforward 😃

Oh my bad, I tried a mdsf --help and didn't see it.

I can see it in mdsf format --help 🤦

Anyway, thanks for adding the linter in the debug

hougesen added a commit that referenced this issue Apr 2, 2024
@ccoVeille
Copy link
Contributor Author

Thanks for implementing it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants