eddyraz

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.

Showing Posts 1 to 10

mcrumm

mcrumm

Phoenix Core Team

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_event and the name in handleEvent. 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

eddyraz OP

Thanks it was a typo, I just edited the post.

mcrumm

mcrumm

Phoenix Core Team

Okay, I’m 0/1 so far, let’s try again! :smiley:

Does the name of the hook object match the value given to phx-hook? In your example they are input_login_token and saveLogintoken respectively.

Since you mentioned that a console.log works in the mounted method I think this is probably not the problem either, but I’m just trying to eliminate all the “simple” stuff.

imkleats

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’s handleEvent call is using the key login_tkn which would be undefined based on the payload coming across the socket.

eddyraz

eddyraz OP

also a type, sorry i have to be more careful when posting.

eddyraz

eddyraz OP

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

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


let liveSocket = new LiveSocket(...)
window.addEventListener(`phx:highlight`, (e) => {
  let el = document.getElementById(e.detail.id)
  if(el) {
    // logic for highlighting
  }
})

Not sure if this is the reason for your problem

eddyraz

eddyraz OP

in the docs says this:

push_event(socket, event, payload)
Pushes an event to the client.

Events can be handled in two ways:

1. They can be handled on window via addEventListener. A "phx:" prefix will be added to the event name.

2. They can be handled inside a hook via handleEvent.

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

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

mcrumm

Phoenix Core Team

Correct. The "phx:" prefix is not part of the event name when using this.handleEvent() on LiveSocket hooks.

To avoid possible issues with JavaScript destructuring while debugging, you could try replacing your handleEvent with the following:

this.handleEvent("saveLoginToken", (payload) => {
  console.log("received payload", payload)
})

…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! :slight_smile: but the more context the better.

Where Next? Top

Trending in Questions Top

Blokh
Hey guys, I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly Do you guys have any suggestions what is the best prac...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
psy-q
I’m trying to set up Emacs with elixir-ls via lsp-mode and credo via Flycheck. This should mostly be preconfigured as Flycheck picks up c...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews