@nrinaudo it's a temporary thing, as we've two artifacts atm: with
Future and F[_] (or finchx)
Yeah
correct?
Actually there's an object in the finch-circe package which should solve this: https://github.com/finagle/finch/blob/master/circe/src/main/scala/io/finch/circe/package.scala#L12-L16
I can't get either to work. i.e. my options are coming back as null still
e.g.
import io.finch.circe.dropNullValues._
val videoCanned: Endpoint[IO, Video] = get(videoadmin :: "canned") {
Ok(Video(9999,"canned","url","link", description = "canned"))
}But the optional null fields still come back as :null
What am I doing wrong?
Thanks
Ah, got it working, just had to be careful with imports
https://gist.github.com/fancellu/b145ed3a0a27c6a1c414c0d485a44d37
is that possible?
I now regret depending on a finagle filter I wrote to guarantee any uncaught exceptions would be formatted the proper way in the response
so I just wrote some stuff that lets me take an Endpoint and run a test as either a Finch endpoint or compile it to a Finagle service and run it
and it more or less works the same
which compiles fine and seems to do what I want. However, I am having trouble getting a call to this endpoint to not 404.
1 reply
private def foo: Endpoint[IO, String] = get(path("debug")) {
None.getOrElse(return BadRequest(???))
Ok("test")
}
This does not typecheck since
return will return the outer function (thus BadRequest(???) is expected to be of type Endpoint[IO, String])
But ideally, we would just return from the lambda passed to
get(...)
as for the pretty-printing there as a toString that kinda does this, but you would have fiddle with the output to get the format you want
"(GET /help :+: (POST /archive :: build-light :+: (POST /archive :: build :+: (POST /fact :: add :: body :+: (GET /fact :: list :+: (GET /scroll :: list :+: (POST /scroll :: apply :: body :+: GET /debug :: situationtheory :: print)))))))"
which is not very helpful
even the parentheses look strangely unbalanced
e.g.
GET /help is a single endpoint
re: your question in Finaglers auto generating developer docs isn't something that is supported at the moment. its a hard problem that we haven't solved. its one of the oldest issues on the repo finagle/finch#73
I'm using finchx 0.32.1. I wrote below code, but unable to understand the reason for compilation error : "Cannot resolve overloaded method"
Can anyone please help me understand? Appreciate the help.
private val greetByName : Endpoint[IO, Json] = get(path("hello") :: paramOption("name")) = {
Ok("Hello".asJson)
}
Hi @zanpakuto. I think the issue is that you are using
paramOption which means the mapper is going to want an argument to the function you are using for mapping. something like this might be what you are looking for: private val greetByName: Endpoint[IO, Json] = get(path("hello") :: paramOption("name"))({ name: Option[String] =>
Ok("Hello".asJson)
})
I have a POST endpoint consuming
jsonBody and decoding via Circe, and I don’t seem to be able to catch the decoding error if it occurs- I want to be able to return a 400 response when bad json is submitted, but the circe DecodingFailure is wrapped in a finch-private CirceError case class. Is there a better approach to achieve this end?