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
f

Filip Wiesner

05/24/2022, 11:03 AM
Possibly dumb question: Is there a way to share fragments between services? I have only one module but want to maintain "module like" behavior between folders in this module. For example I have
feature/home/GetHome.graphql
and
shared/CategoryFragment.graphql
. These files are each in it's own
service
so that I can specify a package name to the generated files. Now I want to access
CategoryFragment
from
GetHome
file but it errors out with `Cannot find fragment `Category``. Or maybe different question with the same outcome. Can I specify the package name of generated file more granularly so that the package names of different queries, mutations and fragments more resemble my defined project package structure?
m

mbonnin

05/24/2022, 11:07 AM
Sounds like you're looking for
packageNamesFromFilePaths()
apollo {
  packageNamesFromFilePaths()
}
f

Filip Wiesner

05/24/2022, 11:08 AM
Oh 🤦‍♂️ I just wasted a few hours if it really is that simple. Thank you
m

mbonnin

05/24/2022, 11:08 AM
It'll use the path to your fragment as a package name:
feature/home/GetHome.graphql => feature.home.GetHome
shared/CategoryFragment.graphql => shared.CategoryFragment
You also can specify a root packageName that will be prepended everywhere
apollo {
  packageNamesFromFilePaths("com.example")
}
You should certainly put everything in a single service if you go that route
There is usually a 1:1 mapping between an Apollo service and a GraphQL schema/endpoint
f

Filip Wiesner

05/24/2022, 11:17 AM
You just saved me, that was exactly what I needed. Thank you very much. Maybe this should be mentioned in
Gradle plugin configuration
chapter in the documentation 🤔
Also, really good job with the library! 👏 I remember using
3.0.0-beta
on some other project but it's completely different story now. And it got a rebrand from Android to Kotlin if I remember correctly.
m

mbonnin

05/24/2022, 1:12 PM
Maybe this should be mentioned in
Gradle plugin configuration
chapter in the documentation
https://github.com/apollographql/apollo-kotlin/pull/4135
❤️ 1
Also, really good job with the library! 👏 I remember using
3.0.0-beta
on some other project but it's completely different story now.
Thanks 😊
f

Filip Wiesner

05/24/2022, 1:21 PM
Maybe this should be mentioned in
Gradle plugin configuration
chapter in the documentation
I meant the official Apollo docs. Or is it planned and this is just a first step?
m

mbonnin

05/24/2022, 1:47 PM
I don't want to give it too much importance as having a flat package name is way more simple, especially if/when you start using multi-modules
f

Filip Wiesner

05/24/2022, 1:47 PM
Fair enough 🤷‍♂️
m

mbonnin

05/24/2022, 1:47 PM
The current Gradle documentation is relatively slim and only outlines a handful of options
We could/should document all the other ones
But in that case, I'd rather do everything all at once
(there are a lot of options down there...)
I was thinking maybe we should "just" copy paste a huge
apollo {}
block with some comments, I've seen other projects do that, it reads quite well
f

Filip Wiesner

05/24/2022, 1:49 PM
Yeah, I was browsing the apollo gradle API while looking for something that could help me 😄
m

mbonnin

05/24/2022, 1:50 PM
Yea, also the fact that groovy users (that are still the majority) do not get any hint doesn't help
f

Filip Wiesner

05/24/2022, 1:51 PM
That is a helpful way but I am afraid a lot of people could just copy that big block without knowing that a lot of stuff is optional. There should be a big disclaimer that it's only for purpose of showing all of the API. But otherwise that would save me a lot of time today 🙂
m

mbonnin

05/24/2022, 1:58 PM
Just curious: was Ctrl-clicking the
Service
class an option for you?
The Kdoc there is more detailed and it shows all the APIs. Ultimately, I wish this would become the source of truth as it can all be done inside IntelliJ
f

Filip Wiesner

05/24/2022, 2:04 PM
Yes, I did "Ctrl-click" to
Service
and tried a few options. I don't know why I didn't find the
packageNamesFromFilePaths
. There is a lot of stuff so I might've just scrolled past it 😕
(that's what I meant by "Yeah, I was browsing the apollo gradle API...")
m

mbonnin

05/24/2022, 2:05 PM
Gotch
f

Filip Wiesner

05/24/2022, 2:06 PM
Maybe I just didn't know what I was looking for so the function name didn't sound like something useful for me
But I don't know how that could be changed so that I would find it 😅 Maybe categorizing the properties/functions somehow? 🤔 Making it more of a DSL rather than huge interface that does everything
m

mbonnin

05/24/2022, 2:11 PM
Yep, we can look into that but it's certainly going to be breaking so for next major release
f

Filip Wiesner

05/24/2022, 2:12 PM
Sounds good 👍 And thanks for your quick help today
m

mbonnin

05/24/2022, 2:15 PM
Sure thing!