Yesod: Using typesafe URLs in AJAX calls

Question

In my Yesod project i have the following route:

/api/hide/thread/#Text/#Int      ApiHideThreadR   GET

I want to request it on the client side with javascript:

function hideThreadCompletely(threadId, board) {
    $.getJSON("/api/hide/thread/"+board+"/"+threadId, function(data) {
        $('#thread-'+threadId).hide();
    });
}

But i can't use @{ApiHideTHreadR} because Yesod requires it's arguments on compile time. What is the proper solution for this, if i want API URLS to look like api/board/1/1 and not api/board?bid=1&tid=1? Keep using manually-defined URL's like "/api/hide/thread/"+board+"/"+threadId?

score 2 · Accepted Answer · answered Sep 27 '13 at 14:54

2

After some searching I found this discussion, where it is suggested that you add the url as a "data-url" attribute to some element. And then load the url from the element. Something like this:

<div id="thread-1" data-hide-url=@{ApiHideTHreadR}>

var url = $("#thread-1").data("hide-url")

answered Sep 27 '13 at 14:54

Tjelle

986
1
9
17

I still need to specify `ApiHideTHreadR`s arguments, so i don't see how this helps me. – arrowd Sep 27 '13 at 19:07

score 1 · Answer 2 · answered Sep 27 '13 at 15:09

1

What I always do is get rid of the explicit parameter passing in the route call and instead replace it with :

getApiHideThreadR::Handler JSON
getApiHideThreadR = do 
  rawTextParam <- lookupGetParam "text"
  rawThreadId  <- lookupGetParam "table"
  (textParam,threadParam) <- someParseFunction rawTextParam rawThreadId
  ...

Then you can use regular ajax style:

$.getJSON("@{ApiHideThreadR}",{text:"sometext",tabe:"sometable"},success()...

For more complex get to haskell type requests: https://github.com/yesodweb/yesod/wiki/Convert-get-params-into-a-haskell-record

Is a nice template.

answered Sep 27 '13 at 15:09

TallerGhostWalt

464
3
11

This would make URL to look like `/api/hide/thread?board=1&thread=2`, but i want `/api/hide/thread/1/2`. – arrowd Sep 28 '13 at 08:08
Yeah I knew that, but it also gives you access to the Text field and Int field you were trying to call... I thought that was the main thrust of the question, not getting it to look exactly like the route syntax. My mistake – TallerGhostWalt Oct 01 '13 at 19:06

fcar · Answer 3 · 2013-09-28T17:07:31.133

1

You can't use a type-safe route to check at compile-time somthing that is known only at run-time. I suspect you know this too, but that is the only sense I can make of your question. Thus, your only option is doing it manually.

edited Sep 28 '13 at 17:07

answered Sep 28 '13 at 12:24

fcar

361
5
13

Yesod: Using typesafe URLs in AJAX calls

3 Answers3

Linked