https://kotlinlang.org
Join Slack
My schema has a field that is defined as a Date, but when looking at the query I'm generating that f...
# apollo-kotlin
c
My schema has a field that is defined as a Date, but when looking at the query I'm generating that fetches that field, it gets resolved to 
Any
. Is there something I'm missing here?
s
What’s the type it has? If it’s not a built-in type that apollo-kotlin knows about, I guess it resolves as 
Any
? Do you have an 
com.apollographql.apollo3.api.Adapter
for it? Perhaps like we do here, with this adapter.
With that said, you may be able to use one of the officially provided optional adapters, as explained here.
c
Am I missing something with adding the adapter?
Copy code
.addCustomScalarAdapter(Date.type, DateAdapter())
doesn't compile.
m
You'll need to register your custom scalar at build time make the codegen aware of the type
Something like:
Copy code
apollo {
  service("service") {
    mapScalar("Date", "java.util.Date", "com.apollographql.apollo3.adapter.DateAdapter")
  }
}
Date
is not in the GraphQL spec so there's nothing special about it, it could be "Any" type by default
The mapping tells the codegen what type to use
If you can, I'd avoid 
java.util.Date
though and prefer 
kotlinx.datetime.Instant
c
Interesting. So I guess I have to ask my serverteam what type 
2023-02-22T20:32:04.000Z
is?
m
"Time is hard" 😅 so I'm not 100% sure but that looks like an UTC instant
s
If it’s following the 
ISO8601
spec, then you’re ok with either.
m
Is the 
Z
part of iso8601? I never know
s
And yeah, this “looks” correct, but I wouldn’t bet on it 😂 I have no idea either
m
That works 🎉
Copy code
val instant = Instant.parse("2023-02-22T20:32:04.000Z")

println(instant.epochSeconds)
@Colton Idle go with 
kotlinx.datetime.Instant
and save you future Java Date troubles
c
Cool. So I'll use KotlinxInstantAdapter
m
Copy code
dependencies {
  implementation("com.apollographql.apollo3:apollo-adapters")
}

apollo {
  service("service") {
    mapScalar("Date", "kotlinx.datetime.Instant", "com.apollographql.apollo3.adapter.KotlinxInstantAdapter")
  }
}
c
Oh. I still need the mapScalar in the build.gradle file?
m
Yep, codegen is decided at build time
c
And then this?
Copy code
.addCustomScalarAdapter(Date.type, KotlinxInstantAdapter)
m
You can actually skip that part because the 3 params 
mapScalar
will "burn" the adapters in the codegen
It's slightly faster because there's no need to lookup the adapter at runtime
c
oh. interesting!
m
(there's also a more simple 
mapScalar(String, String)
without the third parameter that leaves the adapter to be registered at runtime)
c
Is there a way to turn on debugging or logging or something for apollo. after enabling all of this, im not getting any responses anymore and im wondering if something is crashing internally in apollo?
m
We've been trying to stay clear of log statements for these reasons. But there are a few places where you can register hooks. One of the useful ones is adding an OkHttp HttpLogginInterceptor
c
Okay. but any sort of crashes in apollo would likely just crash my app too right?
m
Unless you catch it 😄
Maybe try the query in a unit test? You can then debug
(but you can debug on device too actually)
Just unit tests remove coroutines stuff, lifecycle, etc... could be easier to isolate the issue
c
weird. uninstalled my app and reinstalled and now everything seems to be good to go again
m
I blame cosmic rays 💫 🙂
c
Thought I had it working... 😭 "Cannot access class 'kotlinx.datetime.Instant'. Check your module classpath for missing or conflicting dependencies"
Only dep I added was apollo adapters. hmmmm.
m
apollo-adapters
has an API dependency on 
kotlinx-datetime
so it "should" be seen
Is that an Android Studio thing or command line thing?
s
adapters dependency exposes kotlinx-datetime dependency https://github.com/apollographql/apollo-kotlin/blob/main/libraries/apollo-adapters/build.gradle.kts#L18 so not adding the dep yourself shouldn’t be an issue 👀
c
looks good in studio. but only get that error when i run.
Hm. maybe because my apollo kotlin stuff is in another module, thats used by my main app module. let me change implementation to api for apollo adapters dep 🤞
oooh. that did it. WOOT WOOT
very cool! Thanks everyone for teaching!
while im here. kotlin instant doesn't have 
isBefore
method? I gotta use toJavaInstant? interesting...
m
There is 
.compareTo
I'm pretty sure you can do evrything without going to Java
At least haven't bumped into anything like that just yet
c
Cool. just making sure. new to apollo and kotlin datetime so thats fun. but yeah. im sure google can take it from here. thanks for the quick sanity check!
Had to move to JavaLocalDateTimeAdapter instead. But now getting an exception during runtime from apollo. JavaLocalDateTimeAdapter has an example of: Examples: • "2010-06-01T221944.475" but my date is 
2023-02-22T20:32:04.000Z
so I guess the Z is the culprit making it crash?
hm. Switching to instant makes it work again. Any chance theres an easy way to jsut skip the conversion to a date or time or anything and just go right from a Date to a String?
b
Haha, dates are hard 😅 Well yes you could map it to a String directly with 
mapScalarToKotlinString
in the grade configuration. But in the end you really don't want a string but some kind of date object, right? If you're going to do a conversion, you might as well do it inside an Apollo adapter (if none of the provided ones work for you, you can write a custom adapter).
s
Had to move to JavaLocalDateTimeAdapter instead.
Why?
c
@Stylianos Gakis idk. i kept asking, them seemed to "know" better. lol And @bod thanks! cool about being able to map to a string. teammate suggested that because we apparently have string to date converters in our mapping layer
305 Views
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by