-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Respect formatting options #119
Respect formatting options #119
Conversation
(tabSize | ||
insertSpaces | ||
trimTrailingWhitespace | ||
insertFinalNewline | ||
trimFinalNewlines | ||
key)) |
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.
Not sure, but do we always use this style for structure fields? Or JSON requires 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.
It's intended to be same as the names in LSP specification.
Maybe we can have a macro to automatically converts these names to racket name style.
Then we only use the LSP style names in jsexpr->FormattingOptions
, and racket style names everywhere else.
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.
It would be great if that is possible
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.
What about FormattingOptions
and other top level structs? Their name are also inconsistent with Racket style.
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.
Same, but I think maybe let's have another PR for these changes.
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.
ok. I'm going to rename these fields.
Oh, and as a personal opinion, maybe all |
ok |
The automatic renaming is in progress though. There are some difficulties. It could be in another PR. |
I also rewrote some formatting helper functions. It should fix #112