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

lsp: Enable formatting functionality #643

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

charlieegan3
Copy link
Member

@charlieegan3 charlieegan3 commented Apr 11, 2024

Fixes #638

In #641 support was added to handle textDocument/formatting requests from clients. However, the functionality was disabled for fear that users would see a confusing message:

#638 (comment)

In open-policy-agent/vscode-opa#148 the regal formatter will be used if the user has enabled regal and opa fmt will be used if not. This means that there is only ever one formatter available for rego and the user will see no message.

In #641 support was added to
handle textDocument/formatting requests from clients. However, the
functionality was disabled for fear that users would see a confusing
message:

#638 (comment)

In open-policy-agent/vscode-opa#148 the regal
formatter will be used if the user has enabled regal and opa fmt will be
used if not. This means that there is only ever one formatter available
for rego and the user will see no message.

Signed-off-by: Charlie Egan <charlie@styra.com>
@charlieegan3 charlieegan3 force-pushed the enable-formatting-functionality branch from 9f21105 to f756ea7 Compare April 11, 2024 10:34
@@ -160,7 +160,7 @@ type FormattingOptions struct {
InsertSpaces bool `json:"insertSpaces"`
TrimTrailingWhitespace bool `json:"trimTrailingWhitespace"`
InsertFinalNewline bool `json:"insertFinalNewline"`
TrimFinalNewlines bool `json:"trimFinalNewline"`
TrimFinalNewlines bool `json:"trimFinalNewlines"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🦅👁️

@anderseknert anderseknert merged commit fe1dc3a into main Apr 11, 2024
3 checks passed
@anderseknert anderseknert deleted the enable-formatting-functionality branch April 11, 2024 11:20
srenatus pushed a commit to srenatus/regal that referenced this pull request Oct 1, 2024
In StyraInc#641 support was added to
handle textDocument/formatting requests from clients. However, the
functionality was disabled for fear that users would see a confusing
message:

StyraInc#638 (comment)

In open-policy-agent/vscode-opa#148 the regal
formatter will be used if the user has enabled regal and opa fmt will be
used if not. This means that there is only ever one formatter available
for rego and the user will see no message.

Signed-off-by: Charlie Egan <charlie@styra.com>
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 this pull request may close these issues.

Implement textDocument.formatting
2 participants