Skip to content

Commit

Permalink
Remove xref (not supported)
Browse files Browse the repository at this point in the history
  • Loading branch information
snoyberg committed Apr 5, 2024
1 parent 63c795e commit 3080b71
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion book/asciidoc/routing-and-handlers.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ Consider the following route declaration:
Let's say a user requests the path +/hello/+ – which handler would respond to the request?

It will be +HelloR+ because Yesod's dispatch mechanism removes trailing slashes and
redirects to the canonical form of the URL (see section <<_pieces>>).
redirects to the canonical form of the URL.

If users actually want to address the +HelloNameR+ handler with an
empty string as argument they need to request the path +/hello/-+
Expand Down
2 changes: 1 addition & 1 deletion book/generated-xml/routing-and-handlers.xml
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ should <literal>/foo/bar</literal> route to <literal>Foo1R</literal> or <literal
/hello/#String HelloNameR GET</programlisting>
<simpara>Let&#8217;s say a user requests the path <literal>/hello/</literal> – which handler would respond to the request?</simpara>
<simpara>It will be <literal>HelloR</literal> because Yesod&#8217;s dispatch mechanism removes trailing slashes and
redirects to the canonical form of the URL (see section <xref linkend="_pieces"/>).</simpara>
redirects to the canonical form of the URL.</simpara>
<simpara>If users actually want to address the <literal>HelloNameR</literal> handler with an
empty string as argument they need to request the path <literal>/hello/-</literal>
instead. Yesod automatically converts the Minus sign to the empty string.</simpara>
Expand Down

0 comments on commit 3080b71

Please sign in to comment.