StevenXL
Hello,
I was reading the Phoenix Guides on module plugs here and was confused as to how the module plug example was working. I was going to ask here for help, but in the process I believe I figured it out. (Happy to be corrected if that’s not the case).
I’ll just leave this here in case someone else is confused.
Line -3 (plug HelloPhoenix.Plugs.Locale, "en") is indicating that, when this plug is executed, we will invoke the HelloPhoenix.Plugs.Locale.init/1 function, passing in the argument "en".
The init/1 function will return a value, which will be used as the second argument to HelloPhoenix.Plugs.Locale.call/2.
If the first clause of call/2 matches, then we know that:
- There was a
localeURL parameter - The value of that parameter was in
@locale
We are happy with this so we assign the locale value to the connection.
If the second-clause of call/2 matches, then we know that we need to provide a default, because there was either no locale URL parameter, or the value of it was not in @locale. The default, again, came from whatever init/1 returned, which in the example is "en".
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 2 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
StevenXL
@benwilson512 thank you for the clarification!
benwilson512
This is basically correct, with one minor adjustment.
In most scenarios where
plugis implemented, theinitfunction is actually called exactly once at compile time to setup the options for the plug. Then at runtime when an actual connection is being processed thecallfunction is called on the conn with the opts derived at compile time.