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

un-piping causes CompileError in 1.2.0 #204

Closed
paulswartz opened this issue Nov 21, 2024 · 2 comments
Closed

un-piping causes CompileError in 1.2.0 #204

paulswartz opened this issue Nov 21, 2024 · 2 comments

Comments

@paulswartz
Copy link

Versions

Erlang/OTP 27 [erts-15.1.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1]

Elixir 1.17.3 (compiled with Erlang/OTP 27)

locked at 1.2.0 (styler) 7a8b5e82

Example Input

value
|> Module.function(value2 |> Module.internal_function() |> Module.internal_function2())
|> Module.function2()

re-written to:

value
|> (value2
    |> Module.internal_function()
    |> Module.internal_function2()
    |> Module.function())
|> Module.function2()

with a compile error:

error: undefined function value2/1

Stacktrace / Current Behaviour

Looks like this re-write causes a CompileError: https://github.com/mbta/ride_along/pull/65/files#diff-8e8265b0572eec29f100e902bc4e4dba522b46e8c7d855beaba8c864c4ca7126L75-L82

I'm guessing this was introduced by #133.

@novaugust
Copy link
Contributor

tyty! will have it fixed in a jiffy

@novaugust
Copy link
Contributor

appreciate you taking the time to write this up + giving such a good repro =) 1.2.1 is released with the fix

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

No branches or pull requests

2 participants