So, out of curiosity, I generated another Phoenix project, with mix phx.new project and the results are unfortunately same 
m4hi2
1
code-shoily
Today is being such a hectic day! I still didn’t get the time to try out the chapter. But looking at your code, what is Routes? I don’t see any Routes being aliases on pento_web.ex? Maybe they changed it on 1.7 and you might wanna try the new way of patching? Like mentioned here?
2
cpgo
Thats strange, this is the repo you are using right? https://github.com/m4hi2/pento
Just cloned it and it worked fined (after setting the DB_USER and DB_PASS env vars)
2
ericdouglas
Hi everyone! Very excited to be part of this bookclub 
This will be special to me since I currently work as a javascript/frontend developer, writing React applications for the past few years, but I listened about Elixir years ago and the language together with the Erlang VM changed my brain forever hehe 
I’m genuinely very, very interested to see what possibilities LiveView brings to us to write rich clients (SPA-like) but cohesive applications using one language and one framework, for both the backend and frontend.
I did not start to read the book yet but I’ll this week 
3
code-shoily
so, if you visit here: phoenix_live_view/lib/phoenix_live_view/helpers.ex at main · phoenixframework/phoenix_live_view · GitHub you’ll see that you can go to live_path no longer exists in 0.18. Which is why you were getting that error. Instead,pento_web.ex and set use Phoenix.Router, helpers: true, followed by using wrong_live instead of live_path. Like this:
<%= if @over do %>
<%= live_redirect to: Routes.wrong_path(@socket, :guess) do %>
<button>Try again!</button>
<% end %>
<% end %>
or something like that. Or you could just use the new way and do a
<%= if @over do %>
<.link href={~p"/guess"}>Try Again</.link>
<% end %>
instead.
EDIT: Got to check out why live_path wasn’t working though. I get the same error as you btw. However, I’d prefer using compiled routes and .link.
3
m4hi2
This is strange indeed. Specially since @code-shoily is also facing the same error. I think it’s time to compare Elixir version.
Here’s mine:
Erlang/OTP 25 [erts-13.2] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit:ns]
Elixir 1.14.3 (compiled with Erlang/OTP 25)
I’ve tried this code in both macOS and Ubuntu 20.04.
1
code-shoily
They are running it off your repo so it’s likely their deps are same (unless you didn’t commit lock file). And I don’t think Elixir or Erlang version has anything to do with it 
1
ericdouglas
Just started today reading the book! 
I’ll share my learning strategy so maybe it can be useful to someone.
It consists of 4 steps:
- Read/watch the resource
- Copy the resource
- Transform the resource
- Build a project to validate and consolidate what I learned
1 - Read/watch
In this step, I consume the resource “passively”, without coding.
If I found the content not so good in this first step, I finish there and do not go to the next steps…
2 - Copy the resource
In this step, I copy the content (code) in the exact way the author of the book/course created it. Do not fight with the content. It also prevents you to make a small variation that later will become incompatible with the previous work.
3 - Transform the resource
In this step, I consume the resource again, but now creating a new project that is similar to the one taught. This will force your mind a bit but not too much…
E.g: the book taught you to create a to-do list, so in this step, you will create a book management system, something slightly more difficult.
4 - Build a project to validate and consolidate what I learned
In this final step, you should think about a new project that will use what you learned and maybe add some additional features to go beyond a little more to push your knowledge a little more and help you internalize better what you studied.
7
cpgo
Hey, I just realized that I totally missed the point of your previous messages.
I was just cloning your repo and visiting /guess thats why I was under the impression that everything was fine.
About the live_patch error, I’m also no sure about that, but using the new link component seems to work just fine.
def render(assigns) do
~H"""
<h1>Your score: <%= @score %></h1>
<h2>
<%= @message %> It's <%= @time %>
</h2>
<h2>
<%= for n <- 1..10 do %>
<.link href="#" phx-click="guess" phx-value-number={n}>
<%= n %>
</.link>
<% end %>
</h2>
<%= if @over do %>
<.link patch={~p"/guess"}>Try again</.link>
<% end %>
"""
end
def handle_params(_params, _uri, socket) do
socket = assign(socket, score: 0,
time: time(),
message: "Make a guess:",
secret_number: generate_a_random_number(),
over: false)
{:noreply, socket}
end
1