script
In the phoenix routes we have paths for update/delete like this:
/api/path/:id
Here :id is a wildcard match. How can I mimic this behaviour so that if I have two paths:
"/api/path/123"
I can match above route with this one below.
"api/path/id"
Any regex or pattern matching solution?
Thanks
Trending in Questions
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
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
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Other Trending Topics
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
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
idi527
If I understand you correctly, you can add a more specific route first like this
script
On a side note. Can we get controller name from conn? where request is dispatching.
idi527
Probably,
inspectthe conn, the controller might be inconn.private.phoenix_controllerbut that’s probably an implementation detail and can change in the future …script
I tried that but its not there.
idi527
Have you piped the conn through a router?
allyraza
conn.private.phoenix_controllershould work as expected and should give you the full module nameaxelson
Rather than
conn.private.phoenix_controlleryou should use Phoenix.Controller.controller_module/1allyraza
btw just in case you not aware
Phoenix.Controller.controller_modulealso returnsconn.private.phoenix_controlleraxelson
I am definitely aware of that. But the
privatearea of the conn is for libraries to put data in that they are in charge of. And the actual data that is stored in there is an implementation detail and should not be relied upon directly, otherwise your code may break in a future version of Phoenix.allyraza
you have a valid point about not using private api’s but I was merely correcting what he had stated above