https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
r

roby

04/06/2023, 10:15 PM
Anyone experienced with http4k? I'm trying to add routes with documentation but for somereason the routes are not getting registered?
kt
    val contract = contract {
        renderer = OpenApi3(ApiInfo("Tasks API", "v0.1.0"), Argo)
        descriptionPath = "/docs"

        routes += UserRouter(userService).routes // these dont work
        routes += "/ping" bindContract Method.GET to { _ -> Response(Status.OK).body("pong") } // this works
    }

    val handler = routes("/api" bind contract)
    handler.asServer(Jetty(port)).start() ..

//....

class UserRouter(private val services: UserService) {

    val routes: List<ContractRoute> = listOf(
                "/users/{id}" meta {
            summary = "Get user details"
            returning(
                Status.BAD_REQUEST to "Invalid id",
                Status.NOT_FOUND to "User not found"
            )
        } bindContract GET to ::getUser,
a

Andrew O'Hara

04/06/2023, 10:26 PM
Defining a
ContractRoute
with a path parameter would typically look like
"/users" / idLens meta {
  ...
} bindContract GET to { id ->
  { req ->
    ...
  }
}
I'm not entirely sure if the contract router is unable to route for non-contract path parameters, but fixing that would be the first thing to try.
You can also try adding another route inside the contract that doesn't have a path parameter, as a quick sanity check
r

roby

04/06/2023, 10:38 PM
ok i was able to do it like this:
"/users" / <http://Path.int|Path.int>().of("id") meta {
            summary = "Get user details"
            returning(
                Status.BAD_REQUEST to "Invalid id",
                Status.NOT_FOUND to "User not found"
            )
        } bindContract GET to { id ->
            {
                getUser(id)
            }
        },

// ...

    private fun getUser(userId: Int): Response = errorHandler {
        val res = services.getUser(userId)

        Response(Status.OK)
            .header("content-type", "application/json")
            .body(Json.encodeToString(res))
    }
Isnt there any possible way to still make the lambda receive request parameter?
or do i have to
getUser(id, it)
"/users" / <http://Path.int|Path.int>().of("id") meta {
            summary = "Get user details"
            returning(
                Status.BAD_REQUEST to "Invalid id",
                Status.NOT_FOUND to "User not found"
            )
        } bindContract GET to { id -> { req ->
                getUser(req, id)
            }
        },
idk, this looks a bit awful
a

Andrew O'Hara

04/06/2023, 10:40 PM
Does this give you what you need?
bindContract GET to { id ->
  { req ->
    getUser(id)
  }
}
r

roby

04/06/2023, 10:46 PM
yes, it just looks weird, another problem i am having is for example defining this route:
users/{id}/boards
image.png
adding
/ "boards"
after the path... id thing is throwing error at the whole code
val test = "/users" / <http://Path.int|Path.int>().of("id") / "boards" meta {
        summary = "Get the list with all user available boards"
        returning(
            Status.OK to "User boards",
            Status.BAD_REQUEST to "Invalid id",
            Status.NOT_FOUND to "User not found"
        )
    } bindContract GET to ::getUserBoards
this is getting casted to
Pair<ContractRouteSpec2<Int, String>.Binder, KFunction1<Request, Response>>
(?)
instead of ContractRoute
a

Andrew O'Hara

04/06/2023, 10:55 PM
If you see little benefit in having your path parameters provided by the contract handler in a typesafe manner, then you can omit the extra layer by adding an explicit
Request
type parameter to
req
"/foo" / idLens meta {
  ...
} bindContract GET to { req: Request ->
  Response(OK)
}
The issue with the new route you've added is that you're not handling the value of the new
boards
parameter (even though it's not a lens).
val test = "/users" / <http://Path.int|Path.int>().of("id") / "boards" meta {
  ...
} bindContract GET to { id, _ ->
  { req ->
    Response(OK)
  }
}
Notice the
_
parameter added after
id
. Since we don't care about its value, it can be named
_
and ignored
You may also want to share the id
PathLens
between routes, rather than redefine it each time you add a new route.
r

roby

04/06/2023, 10:59 PM
What does "Lens" mean in this case?
a

Andrew O'Hara

04/06/2023, 11:02 PM
val idLens: BiDiPathLens<Int> = <http://Path.int|Path.int>().of("id")
A lens is a typesafe way to get data in and out of an http message (ie request or response). So to share it, you would so something like:
val getUser = "/users" / idLens bindContract GET
val putUser = "/users" / idLens bindContract PUT
The benefit is that you can reuse the lens in other contracts or in a client call
val response = getUser
  .newRequest(hostname)
  .with(idLens of 123)
  .let(httpHandler)