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

[AUTO] Format files using DocumentFormat #54

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

DocumentFormat.jl would suggest these formatting changes

@@ -822,7 +822,7 @@ function set_variable_request(conn, state::DebuggerState, params::SetVariableArg

if var_ref.kind == :scope
try
ret = JuliaInterpreter.eval_code(var_ref.value, "$var_name = $var_value");
ret = JuliaInterpreter.eval_code(var_ref.value, "$var_name = $var_value")
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't remove the trailing ;.

Copy link

Choose a reason for hiding this comment

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

does removing it change the semantics of the program?

Copy link
Member

Choose a reason for hiding this comment

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

No, but that can't be the criterion, there are countless changes that one could make that don't change the semantics program.

I think we had agreed that the minimal formatter that we want to have in the extension should change whitespacing, indentation and nothing else. In particular, it should never add or remove any other characters that a user wrote.

Obviously this is a great feature to have available in a style and as an option.

@@ -1,5 +1,4 @@
@dict_readable struct InitializedEventArguments <: Outbound
end
@dict_readable struct InitializedEventArguments <: Outbound end
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't remove the line break.

@github-actions github-actions bot force-pushed the create-pull-request/patch branch 2 times, most recently from b7b870a to cdb3fef Compare March 17, 2022 18:32
@github-actions github-actions bot force-pushed the create-pull-request/patch branch 2 times, most recently from e5cdf5a to acb4727 Compare June 29, 2022 07:43
@github-actions github-actions bot force-pushed the create-pull-request/patch branch 3 times, most recently from 81bbecb to 0443fe4 Compare August 18, 2022 22:15
@github-actions github-actions bot force-pushed the create-pull-request/patch branch from a7b5e6b to 7360891 Compare May 2, 2024 22:34
@github-actions github-actions bot force-pushed the create-pull-request/patch branch 8 times, most recently from 0840536 to 2f3fa64 Compare July 3, 2024 14:06
@github-actions github-actions bot force-pushed the create-pull-request/patch branch 3 times, most recently from b22f0b6 to 035310f Compare July 27, 2024 16:26
@github-actions github-actions bot force-pushed the create-pull-request/patch branch 2 times, most recently from c0ef0ea to 9d35b0a Compare August 17, 2024 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants