Databases
StackOverflow2013
Postsdbo
PORails routing: format constraints when none is specified
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails routing: format constraints when none is specified
    primarykey
    data
    text
    <p>For Reasons™, I want to have one controller handle html requests and another handle json api requests.</p> <p>I've got this in my routes:</p> <pre><code>scope module: :api, as: :api do constraints format: :json do resources :users end end constraints format: :html do resources :users end </code></pre> <p>This works great when the url sports a suffix: <code>/users.json</code> goes through my <code>Api::UsersController</code> à la <code>api_users_path</code>; <code>/users.html</code> goes through my <code>UsersController</code> à la <code>users_path</code>.</p> <p>However this does not behave as expected when there is no suffix in the url. Implementing the constraints as lambda show things go wrong:</p> <pre><code>#=&gt; visiting /users scope module: :api, as: :api do constraints -&gt;(request){ puts "In api: #{request.format}"; request.format == :json } do resources :users end end constraints -&gt;(request){ puts "In html: #{request.format}"; request.format == :html } do resources :users end #=&gt; In api: text/html #=&gt; (request.format == :json) =&gt; false </code></pre> <p>and yet it ends up in the api controller.</p> <p>No fiddling with custom constraint classes or lambdas or anything prevents rails from selecting the first route defined if none of the constraints match.</p> <p>I can't find a way to write a constraint that catches when the url lacks a suffix, and I don't feel as if I should have to–<code>request.format == :html</code> reports true when I'm navigating to <code>/users</code>. Why isn't the second constraint catching that?</p> <p>Also, while I could "fix" this by changing the order of these two, I'd much rather know why my constraints aren't working right.</p> <p>Does anyone know how to enforce these constraints differently to effectively switch on whatever the format is, not just the url suffix, or have an explicit constraint that accommodates no format suffix?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Keele
    1. USChris Keele
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails routing: format constraints when none is specified
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails routing: format constraints when none is specified
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails routing: format constraints when none is specified
      1. USChris Keele
      1. VTBountyStart
    1. COthe second contraint cant catch that the route doesnt match
      singulars
      1. PORails routing: format constraints when none is specified
      1. USapneadiving
    2. COwhy dont you simply set the request format yourself for all actions in your api?
      singulars
      1. PORails routing: format constraints when none is specified
      1. USapneadiving
    3. COactually, since you namespace your controller I dont understand why you need route constraints
      singulars
      1. PORails routing: format constraints when none is specified
      1. USapneadiving
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload