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

Better handling of commenting out top-level definition implementation #773

Open
avh4 opened this issue Sep 13, 2022 · 0 comments
Open

Better handling of commenting out top-level definition implementation #773

avh4 opened this issue Sep 13, 2022 · 0 comments

Comments

@avh4
Copy link
Owner

avh4 commented Sep 13, 2022

Example input:

getActiveChildren node =
    []
    -- node.children |> List.filter isActive

Current output:

getActiveChildren node =
    []



--node.children |> List.filter isActive

Desired output:

The commented-out code should remain near the function it belongs to.

TBD

  • do some editors put the -- in column zero when commenting out?
  • should this be determined by indentation? or by line number?
  • is fixing this for top-level definitions enough, or does a similar problem apply to let/case/if/other expressions?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant