-
Notifications
You must be signed in to change notification settings - Fork 26
fix: elixir v1.19 compatible struct update syntax #82
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
Merged
Merged
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
5bce93b
chore: elixir v1.19 compatible pattern matching
StrongFennecs 4b47857
fix: test anon function
StrongFennecs a62d3a3
chore: revert to default tools
StrongFennecs 93bb15d
chore: revert to default tools
StrongFennecs 20542fa
chore: revert to default tools
StrongFennecs e612aab
feat: rm binary oops ;;
StrongFennecs File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,18 +1,19 @@ | ||
| import Slipstream | ||
| import Slipstream.Socket | ||
|
|
||
| socket = connect!(uri: "ws://localhost:4000/socket/websocket") |> await_connect! | ||
| socket = | ||
| connect!(uri: "ws://localhost:4000/socket/websocket") |> await_connect!() | ||
|
|
||
| topic = "rooms:lobby" | ||
| socket = join(socket, topic, %{"fizz" => "buzz"}) |> await_join!(topic) | ||
|
|
||
| _ref = push!(socket, topic, "quicksand", %{"a" => "b"}) | ||
|
|
||
| {:ok, %{"pong" => "pong"}} = push!(socket, topic, "ping", %{}) |> await_reply! | ||
| {:ok, %{"pong" => "pong"}} = push!(socket, topic, "ping", %{}) |> await_reply!() | ||
|
|
||
| push!(socket, topic, "push to me", %{}) | ||
|
|
||
| await_message!(^topic, "foo", _payload) | ||
|
|
||
| socket = leave(socket, topic) |> await_leave!(topic) | ||
| socket |> disconnect() |> await_disconnect! | ||
| socket |> disconnect() |> await_disconnect!() |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For these clauses of
handle_message/1, rather than matching%State{}as the return value, shouldn't we match in the function parameters?I haven't been following the type system stuff lately but I would assume that this would give the type system a better hint about the original
statebinding, and it would know thatstate.joinsexists on this line for example. And thatstate.configexists in clauses below, like the one for%Events.ChannelConnected{}There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah pattern matching in the head is probably a better thing to do,