-
Notifications
You must be signed in to change notification settings - Fork 64
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
More formatter fixes #1851
More formatter fixes #1851
Conversation
Also, handle ``` ``` preformatted blocks.
cf17f5a
to
daa0718
Compare
86d0d62
to
300fb84
Compare
e7729d7
to
ff2f5e1
Compare
It is a little embarassing that I almost pushed code that did this to master. Let us not do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! So we now do change the indentation in the target code blocks as well? I guess it is safe most of the time, but I wonder if there might be some corner cases where we could break the target code. I guess we'll find out eventually 😄
No, I did that using find-and- replace, not using the formatter. |
This addresses some issues raised in lf-lang/playground-lingua-franca#48.
=
signs with whitespace when they are in parameter lists{=
=}
code blocks (fixes Two-space indentation #1847)EDIT: See lf-lang/playground-lingua-franca#50 to view the output of the formatter.