graphql

favila 2022-03-31T17:00:01.797429Z

I’m using lacinia-pedestal in admittedly a very strange way: I’m embedding a pedestal chain/execute call inside of a ring handler using lacina-pedestal’s default interceptors. However I’m running into the problem that many of these interceptors return a :response add a :response to the context, but don’t terminate. It’s almost as if they assume there’s a (chain/terminate-when context :response) somewhere; without this e.g. a query parse error will still attempt to execute the query. Is there an interceptor I’m missing?

steveb8n 2022-03-31T21:21:01.039279Z

I also use the chain in odd ways. had to include this interceptor to emulate an http server in some of my test infra

[io.pedestal.http.impl.servlet-interceptor :refer [terminator-injector]]

steveb8n 2022-03-31T21:21:06.209539Z

maybe that’s it

favila 2022-03-31T21:22:44.128179Z

ah! yeah that’s definitely it

favila 2022-03-31T21:23:59.157949Z

kinda weird it’s only in the servlet impl

favila 2022-03-31T21:25:35.427569Z

ok, this makes me confident that a “normal” server will have this and I’m not doing something odd

favila 2022-03-31T21:25:43.862159Z

thanks3

steveb8n 2022-03-31T21:26:00.803349Z

glad to return the favour. you’ve helped me plenty