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

elixir allows ellipsis in keyword/pair positions #466

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

amchiclet
Copy link
Contributor

Elixir already has ellipsis, but it expects them where identifiers are expected.

But Semgrep also wants to allow ellipsis in other places. This PR allows ellipsis
where keyword/pairs are expected.

Such as function calls foo(kwd_arg1: 0, ...) or map items %{item1: 0, ...}.

Previously, these cases won't parse.

Tested with make test.

Security

  • Change has no security implications (otherwise, ping the security team)

@amchiclet
Copy link
Contributor Author

Something having to do with CircleCI's config causing the workflow to fail.

Locally ran the tests in CircleCI's workflow and they all pass.

@amchiclet amchiclet marked this pull request as ready for review January 12, 2024 02:33
@amchiclet amchiclet requested a review from a team as a code owner January 12, 2024 02:33
@amchiclet amchiclet requested review from mjambon, IagoAbal, aryx and brandonspark and removed request for a team, IagoAbal and mjambon January 12, 2024 02:33
Copy link
Contributor

@brandonspark brandonspark left a comment

Choose a reason for hiding this comment

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

Awesome!

@amchiclet amchiclet merged commit 40c10f7 into main Jan 12, 2024
2 of 3 checks passed
@amchiclet amchiclet deleted the amarin/elixir-fix-ellipsis branch January 12, 2024 20:16
amchiclet added a commit that referenced this pull request Jan 16, 2024
Elixir already has ellipsis, but it expects them where identifiers are expected.

But Semgrep also wants to allow ellipsis in other places. This PR allows ellipsis
where keyword/pairs are expected.

Such as function calls foo(kwd_arg1: 0, ...) or map items %{item1: 0, ...}.

Previously, these cases won't parse.

Tested with make test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants