TwistingTwists
TwistingTwists
put_change pattern for validation and casting in Ecto
2
TwistingTwists
Can someone explain this link component?
<.link> defined here has a method={:delete}
which is using this definition here (as I understand so far) .
- How does this
:deletework? - do we need it even after we specify a call to
:sign_outinhref?
0
mcrumm
Phoenix Core Team
Check out the Phoenix.HTML docs for Link.link/2– You can override the default (:get) link method. You can also provide a data-confirm attribute to prompt the user before following the link. This is all ancient UX stuff that you get when you include phoenix_html.js. 
Almost certainly, but take a look at router.ex to be sure. You don’t want to put destructive actions behind a GET method (especially a public one) otherwise any request to the path will trigger the destructive action. Imagine a search engine spidering your delete links– it’s not ideal.
8
TwistingTwists
easier config management - especially - when you have a lot of configs
1
TwistingTwists
attach function in LiveBeats - needs explanation
I do read the documentation in the cdoe. But what does attaching two modules mean? I see the code is using :telemetry to perform attach and execute handle_execute.
I am not well versed with :telemetry hence unsure about whats’ happening.
handle_execute broadcasts messages. via PubSub. Then why do we need telemetry?
@mcrumm @chrismccord please?
1
en86
Going through this LiveBeats code has been very helpful!
I have a question on memory management. For assigns created in a mount function, it’s simple to use temporary_assigns to clear data that doesn’t need to be tracked.
But what happens when within a LiveView, you create assigns in your HEEX template? For example, within the ProfileLive render function, there is the following code:
<.icon name={:code}/>
.icon is just a standard Phoenix component. Obviously it’s trivial in the case, but is the name assign now in memory being diff tracked with no way of having it cleared from memory since it wasn’t set in the mount function?
0
en86
Reading through the docs now, my understanding is that it is diff tracked (and hence saved in memory).
So maybe for big chunks of data that don’t need to be tracked, best practice is to set in a mount function (and release with temporary_assigns) or pass it as a slot?
0
03juan
I also think this is a great topic and encourage everyone to start threads on investigating other systems of interest. Well done 
I assume this is so you can capture telemetry data at the same time as certain events happen, but if you’re only interested in having parts of the system react to events without capturing the telemetry, you use pubsub.
Another use case could be that when you’re handling the telemetry event you then want to broadcast some other data, or additional data, than what was received from the telemetry event. So you can broadcast a different payload as needed.
0