You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging issues, it would be helpful if users could just write the incorrect changes anyway. This way, when someone sees the message from #463, they can post the incorrect changes to help maintainers replicate and debug the issue. Adding a workaround like this to a local fork of mdformat has been part of my workflow in the past
Proposal
When there is an ast error detected and the CLI argument is provided, mdformat could write to STDOUT
ifopts["write_to_stdout_on_ast_error"]:
sys.stdout.buffer.write(formatted_str.encode())
print_error(
f'Could not format "{path_str}".',
...
The text was updated successfully, but these errors were encountered:
Context
When debugging issues, it would be helpful if users could just write the incorrect changes anyway. This way, when someone sees the message from #463, they can post the incorrect changes to help maintainers replicate and debug the issue. Adding a workaround like this to a local fork of mdformat has been part of my workflow in the past
Proposal
When there is an ast error detected and the CLI argument is provided,
mdformat
could write to STDOUTThe text was updated successfully, but these errors were encountered: