Hey another question regarding lenses in the context of `Ope

Question

Hey another question regarding lenses in the context of `OpenAPI` and `Filter` I have something like ```routes bind contract withFilter FilterWhichWouldLikeToUseALenseInside ``` Sadly I can t use a lens inside of `FilterWhichWouldLikeToUseALenseInside `

dave · Answer

You can just declare a lens outside and just pass it in

DanielZ · Answer

Thanks for your response I don t get it We spend some time on that issue at work When I tried to create a small example it worked fine shrug

dave · Answer

when you say can t use what behaviour are you seeing

DanielZ · Answer

I received a weird message that the parameter has to be a string which it was

DanielZ · Answer

My simplified example is this one ```val nameLens = Path of name val trackingIdLens = Header required tracking id val app = routes status bind GET to Response OK bind contract renderer = OpenApi3 ApiInfo My Application Version 1 0 Jackson descriptionPath = swagger json routes += customerEndpoint withFilter ServerFilters CatchAll then LogRequestName then ServerFilters CatchLensFailure Response BAD REQUEST private fun customerEndpoint = v1 customer name nameLens meta summary = description = headers += trackingIdLens bindContract GET to name String gt request Request gt Response OK body name object LogRequestName operator fun invoke Filter return RequestFilters Tap request Request gt println Filter $ request something nameLens private fun Request something nameLens BiDiPathLens lt String gt = nameLens this fun main println app Request GET v1 customer name marie header tracking id 26 ``` which works fine I don t get why we had an issue today on two different machines smile

dave · Answer

was it body is not a string That s the standard message that comes when using JSON body lenses

DanielZ · Answer

No it was complaining that the path parameter I was looking for wasn t a string I used only path lenses and header lenses in this context

dave · Answer

Then it really doesn t make sense rolling on the floor laughing Let us know if you can recreate it

DanielZ · Answer

Yes I ll try my very best rolling on the floor laughing

DanielZ · Answer

Now I have the issue reproduced ```val nameLens = Path of name val trackingIdLens = Header required tracking id val app = routes status bind GET to Response OK bind contract renderer = OpenApi3 ApiInfo My Application Version 1 0 Jackson descriptionPath = swagger json routes += customerEndpoint withFilter ServerFilters CatchAll then LogRequestName then ServerFilters CatchLensFailure Response BAD REQUEST private fun customerEndpoint = v1 customer name nameLens meta summary = description = headers += trackingIdLens bindContract GET to name String gt request Request gt Response OK body name object LogRequestName operator fun invoke Filter return RequestFilters Tap request Request gt println Filter $ request something nameLens private fun Request something nameLens BiDiPathLens lt String gt = nameLens this fun main println nameLens Request GET v1 customer name marie println app Request GET v1 customer name marie header tracking id 6ed45217 935f 4794 94a5 30b2cfbe181b ``` Output ```Exception in thread main org http4k lens LensFailure path name must be string at org http4k lens Lens invoke lens kt 19 at MyApplicationKt main MyApplication kt 59 at MyApplicationKt main MyApplication kt Caused by java lang IllegalStateException Request was not routed so no uri template present at org http4k routing ExtensionsKt path extensions kt 20 at org http4k lens PathLens$1 invoke path kt 18 at org http4k lens PathLens$1 invoke path kt 17 at org http4k lens Lens invoke lens kt 15 2 more``` Any ideas what I m doing wrong

dave · Answer

Ah yes This is due to the fact you are using both types of routing With the contracts you cannot extract from a path because you re not using a routes block

dave · Answer

The path lenses only pull things out when you are using the routing dsl

dave · Answer

and you ve got name in your path

DanielZ · Answer

ohhhh confused would it work using only contract routes

dave · Answer

With contracts currently the extraction only happens when the path is parsed It s possible we could adjust this but without investigation I m not sure if it would work nicely

DanielZ · Answer

okay thanks a lot for your quick response +1