Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 06:43
    scala-steward closed #649
  • 06:43
    scala-steward commented #649
  • 06:43
    scala-steward opened #652
  • Jan 28 12:51
    TheDIM47 edited #651
  • Jan 28 12:47
    TheDIM47 edited #651
  • Jan 28 08:10
    TheDIM47 edited #651
  • Jan 27 20:03
    TheDIM47 opened #651
  • Jan 25 20:11
    scala-steward closed #630
  • Jan 25 20:11
    scala-steward commented #630
  • Jan 25 20:11
    scala-steward opened #650
  • Jan 23 00:53
    scala-steward closed #648
  • Jan 23 00:53
    scala-steward commented #648
  • Jan 23 00:53
    scala-steward opened #649
  • Jan 20 04:13
    scala-steward closed #642
  • Jan 20 04:13
    scala-steward commented #642
  • Jan 20 04:13
    scala-steward opened #648
  • Jan 19 22:11
    scala-steward closed #645
  • Jan 19 22:11
    scala-steward commented #645
  • Jan 19 22:11
    scala-steward opened #647
  • Jan 14 01:33
    scala-steward closed #614
Eric Meisel
@etspaceman
Perfect, thanks Darren! I will submit that today
Eric Meisel
@etspaceman
@zarthross I have created the PR of the backport, sorry for the wait
Eric Meisel
@etspaceman
image.png
Hello there. Quick question. Are pathVars not supported like query params in terms of Enums? See above. Both use a StringParser based on an Enumeratum enum, but the path param comes through odd
this is on 0.19.1
implicit def producerTypeStringParser[F[_]]: StringParser[F, ProducerType] =
    new StringParser[F, ProducerType] {
      override def parse(
          s: String
        )(implicit F: Monad[F]
        ): ResultResponse[F, ProducerType] =
        try SuccessResponse(ProducerType.withName(s))
        catch {
          case _: NoSuchElementException =>
            FailureResponse.pure[F] {
              BadRequest.pure(s"Invalid ProducerType format: '$s'")
            }
        }
      override val typeTag: Option[TypeTag[ProducerType]] = Some(
        implicitly[TypeTag[ProducerType]]
      )
    }
This is my StringParser FWIW
Kaspar Fischer
@hbf
Hey folks, I'm doing val myIdsList = paramD[List[Long]]("myIds", "Some ids") which works as expected: it parses ?myIds=1&myIds=2 to a List[Long]. However, how can I use my own StringParser[IO, List[Long]] instead of QueryParsers.multipleParse? I'd like to manually parse ?myIds=1,2 to List[Long].
Kaspar Fischer
@hbf

The above came up during an upgrade from v0.19.0 to v0.20.0 where I noticed that suddenly, our custom StringParser[IO, List[Long]] wasn't picked up and instead, QueryParsers.multipleParse was being used.

What I see is that v0.19.0's multiParse() is defined for Seq[_] while v0.20.0's multiParse() is defined for generic B[_].

I also see that QueryParsers.standardCollector and QueryParsers.multiParse are defined in the same scope. Would it help here if standardCollector had higher priority than multiParse()?

Kaspar Fischer
@hbf
Just in case it helps anyone running into a similar problem. I managed to override the default multiParse by defining the following:
  implicit def http4sMultipleParseOverride[A](
    implicit F: Monad[IO],
    p: StringParser[IO, List[A]],
    cbf: Factory[A, List[A]]
  ): QueryParser[IO, List[A]] =
    standardCollector[List[A]](F, p)
Igor Cândido
@IgorCandido
Is there a way to add example/examples to response models without having to manually defining the response model through withSerializers?
Darren Gibson
@zarthross
Not at this time, but it would be a useful feature. Feel free to add a Issue or PR !
Anton Solovyev
@Rosteelton
Hi all! Is there a way to get field names in snake_case in openapi?
ravichax
@ravichax
Hi All, does anyone have examples of the use of genericHeaderCapture to capture generic headers of the form x-custom-header for a Rho route?
Ben List
@listba
Does the latest version of Rho work with the v1.0.0-M3 release of http4s?
Gavin Bisesi
@Daenyth
:wave: What's the plan for the future of the DSL given that symbol literals are deprecated?
Rafał Sumisławski
@RafalSumislawski
Hi @Daenyth
As an alternative to 'foo we've introduced pv"foo". pv stands for pathVar.
You can see an example here https://github.com/http4s/rho/blob/master/examples/src/main/scala/com/http4s/rho/swagger/demo/MyRoutes.scala#L45
Gavin Bisesi
@Daenyth
:+1:
Yotam Hochman
@Yotamho
Hi, I started to use rho and see that when I create a RhoRoutes, I get a logger from it
is there any convenient way to use a different logger (scalalogging's one) but still using the variable name logger ?
Rafał Sumisławski
@RafalSumislawski

Hi @Yotamho
You cloud copy the source of RhoRoutes, and have your own version with the logger field removed. That's what I would do.

Among other options you can also create a block { } inside your class extending RhoRoutes. And while you cannot create a 'logger' field in the class, you can create a val logger in the block, which will shadow the logger field inherited from RhoRoutes. You would then have to put all your code using the logger inside that block. That would work as long as you don't plan having any public members in that class (you can't put public members in the block). It's a bit hacky :P

Kingsley Hendrickse
@kingsleyh
hi - for a List[Long] as the payload in a POST request - it's generating this yaml - which looks incorrect - any ideas on how to solve this?
 - in: "body"
        name: "body"
        description: "List«Long»"
        required: true
        schema:
          type: "array"
          items:
            title: "Long"
            $ref: "#/definitions/Long"
Gavin Bisesi
@Daenyth
that A+circumflex looks like mojibake
are you sure you're generating utf-8 yaml and viewing the file as utf-8
I think that specific character indicates your yaml file might actually be Latin-1 instead of utf-8
If not that, then the inverse
Or CP1252, which is almost the same as Latin-1
Kingsley Hendrickse
@kingsleyh
the items part seems wrong tho
in the doc it makes a list of empty object
I would have thought it should make items with: type: 'Integer', no ref as it's a primitive and then format: 'int64'
like this
  type: "array"
          items:
            type: "integer"
            format: "int64"
Gavin Bisesi
@Daenyth
Oh it's probably because List is a generic and therefore at runtime they get boxed
generics must take subtypes of Object (AnyRef), which primitives are not
Kingsley Hendrickse
@kingsleyh
I see
Gavin Bisesi
@Daenyth
This does feel like something the library should figure out
Kingsley Hendrickse
@kingsleyh
In my case it's quite common to have lists of int or long or string in the payload of POST and PUT requests
Gavin Bisesi
@Daenyth
I think it does get specialized, maybe? I'd open a ticket
Kingsley Hendrickse
@kingsleyh
many of the endpoints were designed way before I started looking at Rho and how to auto generate the docs
yeah - I'm not sure how frequently things get picked up here - maybe I should take a look and send a pull request
thanks for your help :)
Yasuhide Hoshiko
@hoshikon_gitlab
Hi, is there a way to add descriptions to request body or headers? I can't find any documentation nor examples..
Kingsley Hendrickse
@kingsleyh
@Daenyth do you know if it's possible to write the generated yaml / json to a file as well as serving it? Currently the served yaml inherits the authorisation so can't be accessed unless authorised but we want to maybe write it to file and serve it from a non authed endpoint.
jjcapper
@jjcapper
Hey all, quick (and potentially naive) question about using the API. After some digging as to why my swagger docs didn't cover any of the response types, I discovered that if I moved the response code (e.g. Ok(...)) into the body of new RhoRoutes[IO] { ... } then everything started working. So my next question is, how can we achieve this without requiring that everything be written in situ?
At the moment, my best guess is to pass new argument around everywhere (implicit responses: ResponseGeneratorInstances[IO]) and try and use this when declaring the routes? ... E.g. "Description of an endpoint" ** POST / "pathhere" ^ jsonOf[IO,MyType] |>> { (body: MyType) => myDef(body)(this) }
I feel like this can't possibly be the right way to go about it though
Kingsley Hendrickse
@kingsleyh
Ive just started using rho and i found that due to the way it works with implicits i have to put everyhing inside the new RhoRoutes - the only way i found as a workaround was to pass the rho routes into another class and import e.g. import rhoRoutes._ to get all the implicits
Nikita
@nikit-os
Hi all! I have POST endpoint with case classes for request and response. All fields in case classes in camelCase but circe configured to use snake_case. Rho generates definitions in camelCase. How to generate swagger.json with definitions in snake_case?