With this release, Apollo Kotlin now uses Kotlin Native's new memory model. It also contains a number of other improvements and bug fixes.
💙️ External contributors
Many thanks to @glureau
for carefully adding new watch targets
✨️ [new] Kotlin Native: new memory manager (#4287)
Apollo Kotlin is now requiring applications to use the new memory manager, a.k.a. new memory model. Thanks to this change, the restriction that operations had to be executed from the main thread on Apple targets is now removed. You can also use kotlinx.coroutines.test.runTest. Last but not least, benchmarks seem to indicate that performance is better under the new memory manager!
✨️ [new] @targetName
directive (#4243)
This directive was introduced in v3.3.1 to allow overriding the name of enum values in the generated code. It has now been extended to allow configuring the generated name of Interfaces, Enums, Unions, Scalars and Input objects. This can be used to make the generated code nicer to use, or to avoid name clashes with Kotlin types (e.g. Long
) in Kotlin Native.
✨️ [new] Automatic resolution of Apollo artifacts versions from the plugin version (#4279)
From now on, you no longer need to specify explicitly the versions of Apollo dependencies: if omitted, the same version as the Apollo Gradle plugin will be used. This should facilitate upgrades and avoid potential mistakes:
plugins {
plugins {
id("org.jetbrains.kotlin.jvm").version("1.7.10")
id("com.apollographql.apollo3").version("3.5.0")
}
dependencies {
// Replace this
// implementation("com.apollographql.apollo3:apollo-runtime:3.5.0")
// with
implementation("com.apollographql.apollo3:apollo-runtime")
}
}
🚧 [deprecated] runTest
(#4292)
With the new memory model, Apollo's specific runTest
method from apollo-testing-support
is no longer useful and has been deprecated. If you were using it, you should now be able to use Kotlin's runTest
instead, or simply runBlocking
.
🚧 [breaking] Automatic detection of type
enum values.
If you have an enum with a type
value, this value used to name clash with the generated type
property. This version now detects this case automatically and escapes type
to type_
. If you had previously used @targetName
to workaround this issue, you can now remove it to avoid it being escaped twice:
# Remove this
extend enum SomeEnum {
type @targetName(name: "type_")
}
👷 All changes
- Support watchosArm32 (#4260)
- Support @targetName on Interfaces, Enums, Unions, Scalars and Input objects (#4243)
🐘 support lazy APIs for newer AGP versions (#4264)- Pagination: add connectionFields argument to @typePolicy (#4265)
🐘 Get the dependencies version from the plugin automagically (#4279)- Automatically escape
type
in enum values (#4295) - Fix inferred variables in both nullable and non-nullable locations (#4306)
- Native: assume New Memory Manager (#4287)
- Use internal runTest in all tests (#4292)
Version 3.4.0
2022-07-11
This release contains a few important bug fixes (#4214, #4224, #4247, #4256) and makes it possible to compile with Gradle 7.4 and apollo-gradle-plugin
(#4218).
It also introduces incubating
cache artifacts.
💙️ External contributors
Many thanks to @ArjanSM, @zebehringer, @mm-kk-experiments, @mune0903, @stengvac, @elenigen, @shamsidinb and @StylianosGakis for the awesome contributions
✨️ [new] incubating
cache artifacts.
This version introduces the below artifacts:
apollo-normalized-cache-incubating
apollo-normalized-cache-api-incubating
apollo-normalized-cache-sqlite-incubating
These artifacts introduce new APIs to work with cache expiration and pagination (as well as other cache improvements in the future).
These artifacts have no backward compatibility guarantees and most likely have worse performance than the non-incubating artifacts. Documentation will be added once the API stabilize. In the short term, the best place to look for examples are the integration tests:
Note: The experimental withDates: Boolean
argument was introduced in 3.3.1 in the regular artifacts and is removed as part of this release. Use the incubating
artifacts to use it.
👷 All changes
- add TrimmableNormalizedCacheFactory (#4239)
🚧 remove withDates (#4257)🗄️ Chunk parameters in large responses (#4256)- Fix for improper handling of JsonNumber in BufferedSinkJsonWriter (#4247)
- Incubating modules for the next gen cache (#4241)
- Pagination: fixes in FieldRecordMerger and MemoryCache (#4237)
- make it possible to reuse a File Upload (#4228)
- Persist Record arguments/metadata with the SQL Json backend (#4211)
- requestedDispatcher -> dispatcher (#4220)
- Fix test errors were emitted outside the Flow (#4224)
- Make it possible to compile with Kotlin 1.5 and apollo-gradle-plugin (#4218)
🏖️ Relax MapJsonReader endObject, fixes reading inline + named fragments with compat models (#4214)- Introduce RecordMerger (#4197)
- Add @typePolicy(embeddedFields: String! = "") (#4196)
This is a hot fix release that fixes a crash that could happen in the codegen when using responseBased
codegen in a
multimodule setup. It also includes a fix for incorrect generated code when using certain reserved names in enum values.
👷 All changes
Version 2.5.12
is a maintenance release with a fix to restore downloading schemas as SDL, and a fix for Kotlin 1.7 compatibility.
👷 All Changes
This release introduces @typePolicy
on interface/enums, improvements on subscription error handling, and on Test Builders. It also contains a number of other improvements and bug fixes!
✨️ [new] @typePolicy
on interfaces and unions (#4131)
The @typePolicy
directive can now be declared on interfaces and unions. Thank you @bubba for the contribution!
🔌 WebSockets / Subscriptions error handling (#4147)
An issue where websocketReopenWhen
was not called in some cases was fixed. Also, this release introduces SubscriptionOperationException
. A SubscriptionOperationException
will be thrown instead of the more generic ApolloNetworkError
if a subscription fails due to a specific operation error.
📐 Test Builders improvements and fixes
- A DslMarker was added to improve usage with nested builders (#4089)
- When calling a builder, but not assigning it to a field, an error is now thrown, preventing mistakes (#4122)
- The error message displayed when
__typename
is missing was made clearer (#4146) - Fix: use
rawValue
instead ofname
for enums (#4121)
✨️ [new] ApolloClient implements Closable (#4142)
ApolloClient
now implements okio.Closable
so you can use use
with it. Thanks @yogurtearl for this contribution!
✨️ [new] experimental @targetName
directive on enum values (#4144)
If an enum value name is clashing with a reserved name (e.g. type
) you can now use this directive to instruct the codeGen to use the specified name for the value instead. This directive is experimental for now.
✨️ [new] experimental support for renaming directives (#4174)
As we add more client directives, the risk of nameclash with existing schema directives increases. If this happens, you can now import Apollo client directives using @link
:
# extra.graphqls
extend schema @link(url: "https://specs.apollo.dev/kotlin_labs/v0.1")
This adds a @kotlin_labs__
prefix to all Apollo client directives:
{
hero {
name @kotlin_labs__nonnull
}
}
🤖 SqlNormalizedCacheFactory
initialization on Android (#4104)
It is no longer necessary to pass a Context
when initializing the SqlNormalizedCacheFactory
on Android. A Context
is automatically provided, via App Startup.
// Before
val sqlNormalizedCacheFactory = SqlNormalizedCacheFactory(context, "apollo.db")
// After
val sqlNormalizedCacheFactory = SqlNormalizedCacheFactory("apollo.db")
📝 [new] Public API tracking
This release starts tracking the public API of all modules, including MockServer. Even if the API remains experimental, we'll try to keep the number of breaking changes low in the future.
👷 All changes
🐘 publishapollo-gradle-plugin-external
(#4078)- publish the R8 mapping file along the relocated jar (#4085)
- Fix test directories not cleared (#4083)
- Do not use 'header' as a enum value name as it breaks the Kotlin compiler (#4086)
🧪 @experimental support (#4091)- @experimental -> @requiresOptIn (#4175)
- Do not buffer entire body in Http Cache (#4076)
⬇️ add SchemaDownloader.download() (#4088)- add DslMarker for test builders (#4089)
- MockServer: make MockResponse.body a Flow (#4096)
- Issue-3909: add ApolloResponse cache headers (#4102)
- Use rawValue instead of name for enums in test builders (#4121)
💧 first drop for a SQLite backend that stores when each field was last updated (#4104)- Add Operation.Data.toJsonString() convenience function for the jvm (#4124)
- Check for unassigned fields in Test Builders (#4122)
- Add non-breaking spaces after 'return' (#4127)
🧶 Use a getter instead of a const val OPERATION_QUERY (#4130)- Uploads should be read only once even when logging (#4125)
- Keep the 'interfaces' field on the JSON introspection (#4129)
- Allow @typePolicy directive on interfaces and unions (#4131)
- typePolicy on interface: exclude empty keyfields (#4140)
- Sort the type names in the list so the code gen is deterministic. (#4138)
- Use okio.Closable.close instead of dispose on ApolloClient (#4142)
- Parse the interface's interface field in introspection (#4143)
- TestBuilders: improve error message when __typename is missing (#4146)
- Do not bypass websocketReopenWhen {} (#4147)
- SDLWriter: join implemented interfaces with & instead of space (#4151)
- Escape "type" in enums and sealed classes (#4144)
🧰 introduce apollo-tooling and apollo-cli (#4153)- Fix incorrect content-length in MockServer (#4162)
- Allow capitalized field names if flattenModels is true (#4154)
🏷️ Allow namespacing and renaming of directives (#4174)
❤️ External contributors
Many thanks to @tajchert, @asimonigh, @hrach, @ArjanSM, @yshrsmz, @ephemient, @bubba, @eboudrant and @yogurtearl for contributing to this release!
This is the first release with HMPP support. If you're using multiplatform, updating to Kotlin 1.6.21 is strongly encouraged.
This release also brings WebSocket related improvements and other fixes!
✨️ [new] Hierarchical MultiPlatform Project (HMPP) (#4033)
When using Apollo Kotlin on a multiplatform project, this release is compatible with the hierarchical project structure, which makes it easier to share common code among several targets. Using HMPP in your project also fixes some issues when compiling Kotlin metadata. See #4019 and https://youtrack.jetbrains.com/issue/KT-51970/ for more details.
✨️ [new] WebSocketNetworkTransport.closeConnection
(#4049)
This new method can be used in conjunction with reopenWhen
to force a reconnection to the server. This could be useful for instance when needing to pass new auth tokens in the headers. If you were using subscriptionManager.reconnect()
in 2.x, closeConnection
is a simple way to achieve the same behaviour.
✨️ [new] GraphQLWsProtocol.connectionPayload
is now a lambda (#4043)
With GraphQLWsProtocol
, if you need to pass parameters to the connection payload, previously you would pass them as a static map to the builder. With this change you can now pass a lambda providing them as needed. This facilitates passing fresh auth tokens when connecting.
✨️ [new] Add insecure option to download schema (#4021)
You can now use the --insecure
flag when downloading a schema with downloadApolloSchema
, to bypass the certificate check, which can be useful if a server is configured with a self-signed certificate for instance.
👷 All changes
- Add WebSocketNetworkTransport.closeConnection (#4049)
- Made connectionPayload as suspend function in GraphQLWsProtocol (#4043)
⚡ Ignore unknown websocket messages (#4066)- Kotlin 1.6.21 & HMPP (#4033)
- Provide a Content-Length when using Upload (#4056)
☁️ add HttpRequest.newBuilder(url, method) (#4038)- Escape enum constants (#4035)
- Fix the Moshi adapter used for OperationOutput. Moshi cannot get the type parameters from the typealias
automagically (#4022) - Add insecure option to download schema (#4021)
- Try to reduce allocations in MapJsonReader (#3935)
🔒 Deprecate BearerTokenInterceptor and provide tests and docs instead (#4068)
❤️ External contributors
Many thanks to @CureleaAndrei and @kdk96 for contributing to this release!
⚙️ Deprecations
BearerTokenInterceptor
was provided as an example but is too simple for most use cases, and has therefore been deprecated
in this release. This page provides more details
about authentication.- The previous ways of passing parameters to the connection payload with
GraphQLWsProtocol
has been deprecated (see above).
Version 3.2.2
Many thanks to @benedict-lim, @olivierg13, @konomae and @sproctor for their contributions
3.2.2 is a maintenance release to fix the addJvmOverloads
option added in 3.2.0 as well as other fixes. If you're using APQs, the mutations are now always send using POST
. See #4006 for details and a way to override the behaviour if you need to.
👷 All changes
- Use a constant for JvmOverloads to avoid a crash due to relocation (#4008)
- Always use POST for Mutations in APQs (Auto Persisted Queries) (#4011)
- Add configurable headers to WebSocketNetworkTransport (#3995)
- Handle SqlNormalizedCache merge APIs Exceptions with ApolloExceptionHandler (#4002)
- Add adapter for java.time.OffsetDateTime (#4007)
⏰ Add tests for date adapters (#3999)- Fix wrong LocalDate and LocalDateTime formats in JavaTimeAdapters (#3997)
This release introduces a few improvements and bug fixes.
✨️ [new] ApolloCall<D>.emitCacheMisses(Boolean)
(#3980)
When observing the cache with watch
, the behavior was to not emit cache misses at all, which may not desirable in certain cases. With this new option, you can now choose to emit them: in that case responses will be emitted with a null data
.
This can be used like so:
apolloClient.query(query)
.fetchPolicy(FetchPolicy.CacheOnly)
.emitCacheMisses(true)
.watch()
.collect { response ->
// response.data will be null in case of cache misses
}
This is also closer to the behavior that was in place in v2. Many thanks to @mateuszkwiecinski for the insights and raising the issue!
⚙️ [breaking] Allow configuration of frame types used in SubscriptionWsProtocol
and default to Text (#3992)
When using subscriptions over WebSockets with SubscriptionWsProtocol
(the default), the frames were sent in the binary format. It was reported that this was not compatible with certain servers (DGS, graphql-java-kickstart) that are expecting text frames. This is now fixed and the default is to send text frames.
⚠️ This may be a breaking change if your server expects binary frames only!
If that is the case, you can use the newframeType
option to configure the frame type to be sent:
client = ApolloClient.Builder()
.webSocketServerUrl("wss://...")
.wsProtocol(GraphQLWsProtocol.Factory(frameType = WsFrameType.Binary))
.build()
Many thanks to @Krillsson and @aviewfromspace1 for the insights and raising the issue!
👷 All changes
- Allow configuration of frame types used in SubscriptionWsProtocol and default to Text (#3992)
- add
ApolloRequest.newBuilder(operation: Operation<E>)
(#3988) - Add exception handlers to ApolloCacheInterceptor and SqlNormalizedCache (#3989)
📠 Fix some @DeprecatedSince annotations (#3983)👓 add ApolloCall.emitCacheMisses(Boolean) (#3980)⚙️ Fix fragments on the root query type in operationBased codegen (#3973)
❤️ External contributors
Many thanks to @AdamMTGreenberg and @Krillsson for the contributions!
This version adds JS WebSocket support, more options to deal with __typename
amongst other features and bugfixes.
✨️ [new] JS WebSocket support (#3913)
Version 3.2.0 now has WebSocket support for Javascript targets courtesy of @undermark5! This is a huge milestone and means the JS target is now even closer to its JVM and iOS counterparts.
jvm |
Apple | js |
linuxX64 |
|
---|---|---|---|---|
apollo-api (models) |
||||
apollo-runtime (network, query batching, apq, ...) |
||||
apollo-normalized-cache |
||||
apollo-adapters |
||||
apollo-normalized-cache-sqlite |
||||
apollo-http-cache |
The implementation is based on the ws
library on Node and the WebSocket
API on the browser and inspired by Ktor.
✨️ [new] Fine grained __typename
control (#3939)
This version generates non-nullable fragments when it knows the fragment is always present:
{
cat {
# Because Animal is a supertype of Cat this condition will always be true
... on Animal {
species
}
}
}
In addition, it introduces a addTypename
Gradle option to have better control over when to add the __typename
field:
/**
* When to add __typename. One of "always", "ifFragments", "ifAbstract" or "ifPolymorphic"
*
* - "always": Add '__typename' for every compound field
*
* - "ifFragments": Add '__typename' for every selection set that contains fragments (inline or named)
* This is adding a lot more '__typename' than the other solutions and will be certainly removed in
* a future version. If you require '__typename' explicitly, you can add it to your queries.
* This causes cache misses when introducing fragments where no fragment was present before and will be certainly removed in
* a future version.
*
* - "ifAbstract": Add '__typename' for abstract fields, i.e. fields that are of union or interface type
* Note: It also adds '__typename' on fragment definitions that satisfy the same property because fragments
* could be read from the cache and we don't have a containing field in that case.
*
* - "ifPolymorphic": Add '__typename' for polymorphic fields, i.e. fields that contains a subfragment
* (inline or named) whose type condition isn't a super type of the field type.
* If a field is monomorphic, no '__typename' will be added.
* This adds the bare minimum amount of __typename but the logic is substantially more complex and
* it could cause cache misses when using fragments on monomorphic fields because __typename can be
* required in some cases.
*
* Note: It also adds '__typename' on fragment definitions that satisfy the same property because fragments
* could be read from the cache and we don't have a containing field in that case.
*
* Default value: "ifFragments"
*/
You can read more in the corresponding Typename.md design document.
✨️ [new] Maven publishing for multi-module apollo metadata (#3904)
The Apollo Gradle plugin now creates a new "apollo" publication if maven-publish
is found. This means you can now publish the Apollo metadata to a maven repository:
# In your producer project
./gradlew publishApolloPublicationTo[SomeRepository]
Assuming your producer project is using com.example:project:version
for maven coordinates, the Apollo metadata will be published at com.example:project-apollo:version
:
// In your consumer project
dependencies {
implementation("com.example:project:version")
apolloMetadata("com.example:project-apollo:version")
}
Note: There are absolutely no forward/backward compatibility guarantees for Apollo metadata yet. The Apollo version used in the consumer must be the same as the one used in the producer.
✨️ [new] addJvmOverloads
Gradle option (#3907)
For better Java interop, you can now opt-in addJvmOverloads
. addJvmOverloads
will add the @JvmOverloads
to your Kotlin operations:
@JvmOverloads
class GetHeroQuery(val id: String, val episode: Optional<Episode> = Optional.Absent) {
// ...
}
Meaning you can now create a new query from Java without having to specify episode
: new GetHeroQuery("1002")
👷 All changes
📖 Add note to tutorial aboutgraphql-ws
library to tutorial (#3961)- Use ApolloCompositeException for HTTP CachePolicies (#3967)
🖋️ bump kotlin poet to 1.11.0 (#3970)- Add underlying exceptions as suppressed exceptions in ApolloCompositeException (#3957)
- Add macosArm64 and macosX64 targets (#3954)
- JS Websockets: handle remote close (#3952)
⚙️ Introduce addTypename Gradle parameter (#3939)- Optimize CI a bit (#3942)
- Add more field merging diagnostics (#3937)
⚙️ Make adapters code work without relying on having a__typename
IrProperty (#3930)- Add equals and hashCode implementations for models with no properties (#3928)
🐘 Unbreak Gradle configuration cache (#3918)- WebSocket support for JS targets (#3913)
🗄️ add apolloClient.httpCache (#3919)⚙️ Detect case insensitive filesystems (like MacOS default one) and rename classes when that happens (#3911)- Fix exceptions where not caught when reading the body of a batched query (#3910)
🗄️ Fix writing fragments programmatically was using the wrong cache key (#3905)📦 Maven publishing for Apollo metadata (#3904)- Add addJvmOverloads Gradle option for better Java interop (#3907)
🐘 Fix using refreshVersions (#3898)- add support for triple quotes escapes (#3895)
👷 Test Builders: Fix enums in test resolver (#3894)- Validation: Detect missing arguments when there are no arguments at all (#3893)
- Add support for receiving multiple bodies with multipart (#3889)
✅ Validation: allow nullable variables in non-null locations if there is a default value (#3879)🗄️ HttpCache: do not cache mutations by default (#3873)- Chunked Transfer-Encoding support in MockServer (#3870)
- Fix -1 body length in BatchingHttpInterceptor (#3874)
- Fix issue in Java codegen where selectors returned ImmutableMapBuilder instances instead of Map (#3861)
- Make watchers subscribe to the store earlier (#3853)
Version 3.1.0 introduces new APIs for testing, mapping scalars as well a redesigned cache pipeline.
It also contains bugfixes around the @include
directives, MemoryCache and GraphQL validation amongst other changes.
⚙️ [breaking] Fragment package name and useSchemaPackageNameForFragments
(#3775)
If you're using packageNameFromFilePath()
, the package name of generated fragment classes has changed.
Different generated types have different package names:
- Generated types coming from operations are generated based on the operation path
- Generated types coming from the schema (input objects, custom scalars and enums) are generated based on the schema path
Previously, fragments were using the schema path which is inconsistent because fragments are not defined in the schema but are executable files, like operations.
Version 3.1.0 now uses the same logic for fragments as for operations. To revert to the previous behaviour, you can use useSchemaPackageNameForFragments
:
apollo {
useSchemaPackageNameForFragments.set(true)
}
This is also done automatically if you're using useVersion2Compat()
. Moving forward, the plan is to remove useSchemaPackageNameForFragments
in favor of setting a custom PackageNameGenerator
. If you have use cases that require useSchemaPackageNameForFragments
, please reach out.
✨ [New] QueueTestNetworkTransport
(#3757)
3.1.0 introduces QueueTestNetworkTransport
to test at the GraphQL layer without needing to run an HTTP server.
To use it, configure your ApolloClient
:
// This uses a QueueTestNetworkTransport that will play the queued responses
val apolloClient = ApolloClient.Builder()
.networkTransport(QueueTestNetworkTransport())
.build()
You can then use the enqueueTestResponse
extension function to specify the GraphQL responses to return:
val testQuery = GetHeroQuery("001")
val testData = GetHeroQuery.Data {
hero = droidHero {
name = "R2D2"
}
}
apolloClient.enqueueTestResponse(testQuery, testData)
val actual = apolloClient.query(testQuery).execute().data!!
assertEquals(testData.hero.name, actual.hero.name)
✨ [New] MockServerHandler
(#3757)
If you're testing at the HTTP layer, you can now define your own MockServerHandler
to customize how the server is going to answer to requests:
val customHandler = object : MockServerHandler {
override fun handle(request: MockRequest): MockResponse {
return if (/* Your custom logic here */) {
MockResponse(
body = """{"data": {"random": 42}}""",
headers = mapOf("X-Test" to "true"),
)
} else {
MockResponse(
body = "Internal server error",
statusCode = 500,
)
}
}
}
val mockServer = MockServer(customHandler)
✨ [New] FetchPolicy.CacheAndNetwork
(#3828)
Previously, FetchPolicy
s were limited to policies that emitted at most one response. There was a executeCacheAndNetwork()
method but it felt asymmetrical. This version introduces FetchPolicy.CacheAndNetwork
that can emit up to two responses:
apolloClient.query(query)
// Check the cache and also use the network (1 or 2 values can be emitted)
.fetchPolicy(FetchPolicy.CacheAndNetwork)
// Execute the query and collect the responses
.toFlow().collect { response ->
// ...
}
✨ [New] ApolloCall<D>.fetchPolicyInterceptor(interceptor: ApolloInterceptor)
(#3743)
If you need more customized ways to fetch data from the cache or more fine-grained error handling that does not come with the built-in FetchPolicy
, you can now use fetchPolicyInterceptor
:
// An, interceptor that will only use the network after getting a successful response
val refetchPolicyInterceptor = object : ApolloInterceptor {
var hasSeenValidResponse: Boolean = false
override fun <D : Operation.Data> intercept(request: ApolloRequest<D>, chain: ApolloInterceptorChain): Flow<ApolloResponse<D>> {
return if (!hasSeenValidResponse) {
CacheOnlyInterceptor.intercept(request, chain).onEach {
if (it.data != null) {
// We have valid data, we can now use the network
hasSeenValidResponse = true
}
}
} else {
// If for some reason we have a cache miss, get fresh data from the network
CacheFirstInterceptor.intercept(request, chain)
}
}
}
apolloClient.query(myQuery)
.refetchPolicyInterceptor(cacheOnlyInterceptor)
.watch()
.collect {
//
}
✨ [New] Service.mapScalar
Gradle API (#3779)
You can now use mapScalar
to specify your scalar mappings:
apollo {
// Replace
customScalarsMapping.set(mapOf(
"Date" to "java.util.Date"
))
// With
mapScalar("Date", "java.util.Date")
}
mapScalar
also works with built-in scalar types so you can map the ID
type to a kotlin Long:
apollo {
// This requires registering an adapter at runtime with `addCustomScalarAdapter()`
mapScalar("ID", "kotlin.Long")
}
As an optimization, you can also provide the adapter at compile time. This will avoid a lookup at runtime everytime such a scalar is read:
apollo {
// No need to call `addCustomScalarAdapter()`, the generated code will use the provided adapter
mapScalar("ID", "kotlin.Long", "com.apollographql.apollo3.api.LongAdapter")
}
For convenience, a helper function is provided for common types:
apollo {
// The generated code will use `kotlin.Long` and the builtin LongAdapter
mapScalarToKotlinLong("ID")
// The generated code will use `kotlin.String` and the builtin StringAdapter
mapScalarToKotlinString("Date")
// The generated code will use `com.apollographql.apollo3.api.Upload` and the builtin UploadAdapter
mapScalarToUpload("Upload")
}
🚧 [Changed] convertApolloSchema
and downloadApolloSchema
now use paths relative to the root of the project (#3773, #3752)
Apollo Kotlin adds two tasks to help to manage schemas: convertApolloSchema
and downloadApolloSchema
. These tasks are meant to be used from the commandline.
Previously, paths were interpreted using the current working directory with File(path)
. Unfortunately, this is unreliable because Gradle might change the current working directory in some conditions (see Gradle#13927 or Gradle#6074 for an example).
With 3.1.0 and onwards, paths, will be interpreted relative to the root project directory (project.rootProject.file(path)
):
# schema is now interpreted relative to the root project directory and
# not the current working directory anymore. This example assumes there
# is a 'app' module that applies the apollo plugin
./gradlew downloadApolloSchema \
--endpoint="https://your.domain/graphql/endpoint" \
--schema="app/src/main/graphql/com/example/schema.graphqls"
❤️ External contributors
Many thanks to @dhritzkiv, @mune0903, @StylianosGakis, @AchrafAmil and @jamesonwilliams for their awesome contributions! You rock
👷 All changes
- Fix error reporting when there is a "schema.graphqls" but it doesn't contain any type definition (#3844)
- Make guessNumber read the next value only once, fixes parsing custom scalars without a custom adapter (#3839, #3836)
- Clarify need to pass client's customScalarAdapters to store methods (#3838)
- Fix null pointer exception in LruCache while trimming (#3833)
- Add FetchPolicy.CacheAndNetwork (#3828)
- Allow to specify error handling for watch() (#3817)
- Scalar mapping and adapter configuration improvements (#3779)
- Tunnel variables in CustomScalarAdapters (#3813)
- Terminate threads correctly if no subscription has been executed (#3803)
- fix validation of merged fields (#3799)
- Make
reconnectWhen
suspend and pass attempt number (#3772) - Merge HTTP headers when batching (#3776)
- MockServer improvements and TestNetworkTransport (#3757)
- Fix calling ApolloClient.newBuilder() if the original ApolloClient used
.okHttpClient
(#3771) - Make
convertApolloSchema
anddownloadApolloSchema
use path from the root of the project (#3773, #3752) - fix fragment package name in multi-module scenarios (#3775)
- Make the error printer robust to unknown source locations, fixes schemas with duplicate types (#3753)
- Allow to customize the fetchPolicy with interceptors (#3743)