chan11347
Print all data out
todo_server = [
%{date: ~D[2020-05-19], id: 1 ,time: ~T[16:52:00], title: "Shopping"},
%{date: ~D[2020-05-19], id: 2 ,time: ~T[16:52:00], title: "thinking"},
%{date: ~D[2020-05-20], id: 3 ,time: ~T[16:52:00], title: "Drinking"},
%{date: ~D[2020-05-20], id: 4 ,time: ~T[16:53:00], title: "swimming"}
]
i have 4 different value, so i can use
def time_check(todo_server, time) do
GenServer.call(todo_server, {:time_check, time})
end
i have a function can print out the whole result with the time i asked for
Todo.Server.time_check(todo_server, ~T[16:52:00])
return
[
%{date: ~D[2020-05-19], id: 1 ,time: ~T[16:52:00], title: "Shopping"},
%{date: ~D[2020-05-19], id: 2 ,time: ~T[16:52:00], title: "thinking"},
%{date: ~D[2020-05-20], id: 3 ,time: ~T[16:52:00], title: "Drinking"}
]
but how to print our the whole todo_server? by
def show_all(x) do
IO.inspect(x)
end
?
Most Liked
lucaong
So you want to see all values in the todo_list part of the GenServer state (that’s different from “the value of todo_server”, as todo_server in your time_check function is the pid or name of a GenServer process).
Here is the code from your previous message:
def handle_call({:show_all}, _, {name, todo_list}) do
{:reply, Todo.List.show_all(todo_list), {name, todo_list}}
end
You are matching on the message {:show_all}, so you need to issue the following call: GenServer.call(todo_server, {:show_all}).
Note that there are a couple of more things you could improve, not related to the main question though:
-
Your message is a tuple of a single element,
{:show_all}. It’s not really necessary to wrap the message in a tuple, if it’s made of a single value: you could just send directly the atom:show_allinstead. Of course, if you change this, the message that you send inGenServer.callshould match the one that you pattern match inhandle_call. -
Instead of printing the list with
IO.inspect, you could just return it, and in case let the caller print it.
kip
As @lucaong pointed out, the message you send must have a matching function head. In this cas you are sending the message :show_all but you are only expecting a message {:show_all}. They are not the same.
For this class of error the messages are pretty clear I think so its good to get comfortable with reading function clause errors.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #javascript
- #code-sync
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









