eddyraz
good Afternoon, I have a live_view component with a input hidden field “attached” to a phx-hook
1–in the template:
<form id="login_form" phx-submit="check_login_credentials">
<input type="hidden" id="login_token" phx-hook="input_login_token"/>
.
.
.
</form>
2–in the server:
there’s a function handle_event/3 that processes the username and password and send it to an external Auth API in Django using djoser REST API. and receives a token.
def handle_event("check_login_credentials", params, socket) do
login_tkn="823703847509432870598743205987" #test dummy data
if login_tkn do
{:noreply, push_event(socket, "saveLoginToken", %{login_token : login_tkn}
.
.
.
end
end
3—in the hooks file app.js theres a hook declared who manipulates the data sent from the server
let hooks = {}
hooks.saveLogintoken ={
mounted() {
localStorage.clear()
this.handleEvent("saveLoginToken", ({login_tkn}) => localStorage.setItem("login_token", login_tkn)
},
};
When I put a console.log(something) in after the mounted() section it prints in the console, but any code put in this.handleEvent() section is not executed, If i take the other aproach and use
this.el.addEventListener("input", e => {....} it works but not handleEvent
could anybody explain why is not working, thanks in advanced.
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Is there any way to avoid the Hologram compiler running when using iex? It seems like the front-end code could potentially be disregarded...
New
** (ArgumentError) expected :max_attempts to be a positive integer, got: {:@, [line: 10, column: 19], [{:max_attempts, [line: 10, column:...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mcrumm
Hi @eddyraz! I am not sure if this is the actual issue, but in your example I noticed a typo between the event name in
push_eventand the name inhandleEvent. Is that difference present in your actual code as well? If so, does using the same event name in both places allow the handleEvent call back to be invoked?eddyraz
Thanks it was a typo, I just edited the post.
mcrumm
Okay, I’m 0/1 so far, let’s try again!
Does the name of the hook object match the value given to
phx-hook? In your example they areinput_login_tokenandsaveLogintokenrespectively.Since you mentioned that a console.log works in the
mountedmethod I think this is probably not the problem either, but I’m just trying to eliminate all the “simple” stuff.imkleats
There’s one other typo that could be problematic if it’s not just erroneous transcription.
The event payload in the Elixir side has a key of
login_token, but the object destructuring on the JS side’shandleEventcall is using the keylogin_tknwhich would beundefinedbased on the payload coming across the socket.eddyraz
also a type, sorry i have to be more careful when posting.
eddyraz
I also changed that(it was that way in the code), but still no reults. I read the Javascript interoperability in Liveview hexdocs (JavaScript interoperability — Phoenix LiveView v1.2.5), but still no clue why isn’t working.
Terbium-135
If you are using push_event:
Phoenix Liveview adds the string
phx:in front of the event name.So
"saveLoginToken"becomes"phx:saveLoginToken"Have a look at
with the topic: Handling server-pushed events
Not sure if this is the reason for your problem
eddyraz
in the docs says this:
So I think as I am using the hook aproach it must work without the
"phx:"prefix I keep looking for a reason this is not working.codeanpeace
The key you set here is
login_token…… while the key you seem to be unpacking on via destructuring assignment here is
login_tkn.Give this a shot:
this.handleEvent("saveLoginToken", ({login_token}) => localStorage.setItem("login_token", login_token)mcrumm
Correct. The
"phx:"prefix is not part of the event name when usingthis.handleEvent()on LiveSocket hooks.To avoid possible issues with JavaScript destructuring while debugging, you could try replacing your handleEvent with the following:
…other than that, it is hard to say without having more of the code in context. Would it be possible for you to copy/paste some large blocks of code directly from your project? Please remove anything you can’t share, of course!
but the more context the better.