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

Fix: Erlang function calls in pipes were incorrectly formatted #476

Merged
merged 1 commit into from
Nov 8, 2023

Conversation

scohen
Copy link
Collaborator

@scohen scohen commented Nov 7, 2023

Erlang remote calls were not being recognized as being in a pipeline context because they're just atoms, and that wasn't included as a valid token inside of pipelines. Thus, in_context?(x, :pipe) would return false, and the first arguments to the functions would appear

Fixes #475

Erlang remote calls were not being recognized as being in a pipeline
context because they're just atoms, and that wasn't included as a
valid token inside of pipelines. Thus, `in_context?(x, :pipe)` would
return false, and the first arguments to the functions would appear

Fixes #475
@scohen scohen added this to the 0.4.1 milestone Nov 7, 2023
@scohen scohen merged commit 92f1434 into main Nov 8, 2023
7 checks passed
@scohen scohen deleted the fix-remote-erlang-pipelines branch November 8, 2023 16:07
scohen added a commit that referenced this pull request Nov 8, 2023
Erlang remote calls were not being recognized as being in a pipeline
context because they're just atoms, and that wasn't included as a
valid token inside of pipelines. Thus, `in_context?(x, :pipe)` would
return false, and the first arguments to the functions would appear

Fixes #475
scohen added a commit that referenced this pull request Nov 9, 2023
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.

Erlang remote calls aren't completed correctly in pipelines
2 participants