Add tlaplus-formatter support#327
Conversation
b2f1fed to
a25fdf9
Compare
2866e79 to
069d5c4
Compare
606f3fc to
6213ee1
Compare
|
what is the status quo on this one? |
|
I don't think there is much to do here until the tlaplus formatter package (or other formatters) gets into a more mature state and becomes worth integrating into the plugin. |
|
@FedericoPonzi A couple of months have passed, and it appears that you’re preparing a 0.1 release. Perhaps it’s time to revisit this PR? |
65e7901 to
a38d36d
Compare
a38d36d to
0d0b8be
Compare
|
The formatter can’t come soon enough. Critics have argued that TLA+ hasn’t kept up with modern tooling standards, and the lack of a formatter is often mentioned as a concrete example. |
Signed-off-by: Federico Ponzi <me@fponzi.me>
0d0b8be to
5eba297
Compare
younes-io
left a comment
There was a problem hiding this comment.
I also was looking for a commit and couldn't find it; so not sure if history in this branch was re-written..
|
I usually amend and work on the same commit. I've added a new commit to address your last comment now, thank you! |
Signed-off-by: Federico Ponzi <me@fponzi.me>
6f46cd6 to
532f026
Compare
younes-io
left a comment
There was a problem hiding this comment.
LGTM. Thank you @FedericoPonzi
|
Can't wait to give this a spin. :-) Should also be on the list at tlaplus/tlaplus#1311 |
|
I'm happy to see the initial version merged finally :) I know it's not perfect yet, so please do share feedback and it can be improved over time |
|
|
Add support for the tlaplus-formatter to the vscode-extension. It is enabled by default. It reuses the module search paths that the user has configured. After each formatting, the formatter verifies the ast is valid and matches the one from before - if the check fails the old spec is produced in output, so it's safe to use. It can be disabled via settings, and it's enabled by default.