gilbertbw
Using conditionally compiled routes with verified routes
I have added a page that is only available in development
defmodule MyWeb.Router do
use MyWeb, :router
...
# Enable LiveDashboard and Swoosh mailbox preview in development
if Application.compile_env(:tax_comps, :dev_routes) do
import Phoenix.LiveDashboard.Router
scope "/dev" do
pipe_through :browser
get "/myroute", MyWeb.DevMyRouteController, :blah
post "/myroute", MyWeb.DevMyRouteController, :blah
end
end
end
this renders a form
<.simple_form :let={_form} for={@conn.params["blah_request"]} action={~p"/dev/myroute"} >
<.input type="textarea" name="stuff" value={@stuff} label="Stuff?"/>
<:actions>
<.button name="separate" value="false">Go</.button>
</:actions>
</.simple_form>
When running mix test --force I am getting
warning: no route path for MyWeb.Router matches "/dev/myroute"
I belive I could use the route helpers but I see this is deprecated, and in my Phoenix 1.17 project these helpers are disabled by default.
What is the recommended way to fix this?
Marked As Solved
josevalim
You can always use non-verified routes for those, by removing the ~p sigil, especially if they are dev only (so any mistake only affects dev, which you can quickly address).
Also Liked
sodapopcan
Oops sorry that was a very unfortunate typo. I meant make them UNavailable in production, ie, they will work in any other env. ie if Mix.env() != :prod, do: # ....
D4no0
As @sodapopcan mentioned, checking that the env is not prod is a very good solution.
To formulate on why you are getting this warning: this is due the fact that you have defined dev_routes only in dev.exs configuration. The tests are not using dev configuration by default, but its specific one that is test.exs, hence making those routes unavailable in the test environment.
As an alternative to the solution that was provided above, you could add dev_routes and set it to true in your test configuration, however I would always go with the solution that checks that the env is not prod, as it has much smaller footprint and it is times more readable.
As a word of warning, if this warning comes from your application code (as opposed to your tests) then you are most probably doing something wrong, you shouldn’t use environment specific routes in application code, as that would imply that the functionality using it will not work correctly across all environments.
sodapopcan
This doesn’t seem like a great practice to me. In this case it’s perhaps harmless, but it doesn’t set a good precedent as it means test is inconsistent with dev in non-obvious ways. Perhaps I’m overthinking it 
Popular in Questions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
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 for Elixir devs who love to ship. Start your free account.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"