@korny feel free to just use edge 😉

Hey folks - I'm looking at making a really simple hacky json API for an internal company hackathon - it doesn't need to do much at all beyond accepting POSTS with json payloads and return JSON responses. I'd like to keep my example really simple, along the lines of a Sinatra app. What's the minimum to do this in Yada/Bidi?

boilerplate for yada is prtty small, yada/listener covers the bulk.

(yada/resource
  {:methods
    {:post {:response "application/json" :accepts "application/json" :response (fn [ctx] {:hello "world"})}})

It feels like the docs jump straight from "here's a sample with no routes" to git clone edge 🙂

& it will handle content negotiation & failure if clients ask for edn or somewhat

yada doesn't handle routes, period. bidi docs should cover that for you though 🙂

@korny noted. Good feedback!

@dominicm I get that - but that's not particularly a great demo for me to say "hey, this is as easy as your Sinatra example. Oh, hang on, you need to look at this other projects for routes" 🙂

I should say I like the separation between the two. And "being like Sinatra" isn't a goal for yada!

yada depends on bidi

So you just need to depend on yada

ah, megayada.

Architecturally they are separate libs but yada 'know' about bidi and provides some extra features if it's present

I suspect I'll just git clone edge then delete all the bits I don't want. I'm just lazy and hoped someone else had already done this 🙂

s/lazy/baby-driven-sleep-deprived/g

The ext mechanism means you can have a yada which eliminates bidi completely. But that's just a technical point. Yada 'full' comes batteries included with bidi. Fine for hackathons.

Edge is intended to show 'full stack' including the great adzerk cljs reloading and browser repl figwheel-style experience

Overkill for a sinatra-like backend

@korny I was trying to find the emoji for 'I know the feeling' but then Bruce came up

embraces all human feelings

I have something like that locally, but I added stuff to it 😛

I feel a boot-new template coming on 😄

So cool that someone made an emoji for Bruce!

I'm submitting it to the Unicode Standard to be in v9

Yeah. The Edge thing is great for full stack (needs a db layer though)

But would be great to have a stripped down version

It would be a lot simpler

@dominicm Does Yada really handle content negotiation? I tried to coerce a 406 Not Acceptable out of Yada by sending a request with a Accept: application/edn header to a resource which only produced json i.e. :produces "application/json". The only thing Yada checked as far as I could tell was that the request body was on the accept-format specified in the resource.

I ended up creating my own interceptor to handle 406 responses. Edit: Would be nice to not have to do that.

If you only produce EDN but the client asks for JSON it's a 406

Yada supports content negotiation.

(Took me a whole summer to implement properly)

Well, I'l be damned if it does not work without my interceptor. I must have missed something when testing this earlier on. Thank you both for the clarification.

deleting code is the best pr

Can I somehow do a “server-side” redirect instead of returning 302 and letting the client do a new request?

In my case, I need all uri ending in “/” to redirect to the uri without the “/”. I could do a regex on all routes, but that seems a bit like a lot of local fixes to a global problem

A 302 is a global solution, but that won’t work behind a proxy

What is a server-side redirect?

Hmm, well, a redirect that the server (yada) takes care of, eg it does not involve the client. So it’s a kind of an alias of a uri

Server-side is probably not the correct frase

Ah, okay. Multiple routes for the same resource?

Redirect made me think 30{2,1}

Yes, exactly. 30x was what I’m using, but that gives me trouble with nginx.

Why's that :thinking_face:

Well, my service is serving stuff like /some-resource, but that gets prepended with /api/some-resource by nginx.

So only nginx know the correct “full” path from the client’s point of view.

Of course, nginx could do a redirect instead. Which might be the way to solve it.

ah, hadn't ever considered that. Surprised nginx can't prepend onto that sort of thing.

There’s probably a way to do what I want with nginx. But it’s more fun to solve in clojure 😉

But is there a way to do multiple routes for the same resource in some global way?

I mean, this will be a bidi solution I think.

The simplest way I can think of is a function which takes the "pattern" and doubles it up:

(defn double-vision
  [pattern]
  #{pattern (concat pattern ["/"])})

Might need to handle non-nested too, something like:

(if-not (sequential? pattern)
  (vector pattern)
  pattern)

Cool, I think I understand that. I’ll try it out!

Basically, it will take this: [(double-vision ["/some-resource"]) (fn [req] …)] and generate [#{["/some-resource"] ["/some-resource" "/"} (fn [req] …)]

You probably want (double-vision "/some-resource") to work too though. So that's why you might add a sequential? check.

Maybe even vector?