Skip to content

Releases: apollographql/apollo-ios

1.3.3

01 Aug 19:17
c3f6951
Compare
Choose a tag to compare

Fixed

  • Fix two issues with generated models: See PR (#3168). Thank you to @iAmericanBoy for finding these issues and providing a reproduction case.
  • Fix computation of operation identifiers for persisted queries: See PR (#3163). Thank you to @WolframPRO for finding these issues.

1.3.2

20 Jul 22:11
97ad4f5
Compare
Choose a tag to compare

Improved

  • Throw an error when an invalid key is present in the codegen configuration JSON (#2942): See PR (#3125) Thank you to @Iron-Ham for the contribution.
  • Cleanup unused imports and declarations. (#3099): See PR (#3100) Thank you to @Iron-Ham for raising the issue and contributing the fix.
  • Improvement to response code error API (#2426): See PR (#3123). Thank you to @dfperry5 for the contribution.
  • Improved file path support for operation manifest generation: See PR (#3128)

Fixed

  • Fix two issues in test mock generation: See PR (#3120). Thank you to @TizianoCoroneo for finding this issue and contributing the fix.
  • Fixed precondition failure when surpassing graphql-js max error count (#3126): See PR (#3132).

Deprecated

  • Deprecated queryStringLiteralFormat in ApolloCodegenConfiguration: Query string literals will now always be generated as single line strings. See PR (#3129).

1.3.1

12 Jul 21:20
93b6578
Compare
Choose a tag to compare

Fixed

Deprecated

  • Deprecated APQConfig & operationIdentifiersPath in ApolloCodegenConfiguration.
    • These have been replaced with OperationDocumentFormat and OperationManifestFileOutput respectively. Please see the documentation for ApolloCodegenConfiguration for more information.

1.3.0

20 Jun 19:55
84d797e
Compare
Choose a tag to compare

Though 1.3.0 is a minor version bump, some critical issues were addressed in this version that requires a small breaking change during the upgrade. While we strive to make the upgrade path for minor versions seamless, these issues could not be reasonably resolved without requiring this migration.

For a detailed explanation of the breaking changes and a guide on how to migrate to 1.3.0, see our migration guide.

Breaking

  • Using reserved keyword Type as in selection fields does not compile (#3006): See PR #3058. Thank you to @Nielssg for raising the issue.
  • Memory leak from InterceptorRequestChain when ending the chain with returnValueAsync (#3057): See PR #3070. Thank you to @marksvend for raising the issue.

1.2.2

15 Jun 20:30
a3a1eae
Compare
Choose a tag to compare

Added

  • Support SOCKS proxies for debugging websocket based subscriptions(#2788): Thank you to @tahirmit for the contribution.

Fixed

  • Fix conversion of generated models into nested type cases (#2989 & #2980): In some cases, the generated models were missing types when calculating which fragments were fulfilled for a selection set. This was causing type case conversion to return nil incorrectly. See PR #3067. Thank you to @tgyhlsb and @dafurman for raising these issues.
  • Fix crashes in code generation when merging fragments at definition root (#3071): When fragments with type conditions were defined on the root of an operation or named fragment, the code generation engine was crashing. See PR #3073. Thank you to @tahirmit for raising and helping us reproduce this issue.
  • Fix parsing of input objects as default values for input params (#2978): The codegen engine will no longer crash in this situation. Thank you to @ecunha-ta for raising the issue.

1.2.1

02 Jun 18:56
759a665
Compare
Choose a tag to compare

Improved

  • Added new validation to alert users to type naming conflict when running code generation(#2405): See PR #3041.

Fixed

  • Int values failing to cast to Scalar Type during cache key resolution (#3034): See PR #3037. Thank you to @asbhat for raising the issue.
  • Fix malformed RootEntityType on generated fragment with @include condition. (#2962): See PR #3045. Thank you to @alexisbronchart for raising the issue.

1.2.0

16 May 02:24
Compare
Choose a tag to compare

Though 1.2 is a minor version bump, a critical problem was addressed in this version that requires a small breaking change during the upgrade. While we strive to make the upgrade path for minor versions seamless, this issue could not be reasonably resolved without requiring this migration.

For most users, this migration will only require a single change to your SchemaConfiguration.swift file.

For a detailed explanation of the breaking changes and a guide on how to migrate to v1.2, see our migration guide.

Breaking

  • Cache Key Configuration API Changes (#2990): The API for configuring custom cache keys has had a minor change in this version. The signature of the cacheKeyInfo(for:object:) function, defined in your generated SchemaConfiguration.swift file, has been modified. For more information, see our migration guide.

Improved

  • Improved performance of GraphQL execution (#2990): Improvements to the GraphQLExecutor resulted in a ~15-20% reduction in execution time for parsing and mapping network response or cache data onto generated models.
  • Improved performance of generated model initialization and type conversions (#2990): The DataDict used to store the data for generated models has been updated to use copy-on-write value semantics. This resulted in a ~70-80% reduction in the execution time of initialization and type case conversions in the generated models.

Fixed

  • Pruning generated files for .relative(subpath:) operations (#2969): See PR #2994. Thank you to @jimisaacs for raising the issue.
  • InputObjects generated with incorrect getter/setter key (#2858): See PR #2996. Thank you to @Austinpayne for raising the issue.
  • Generates conflicting types for fields of singular and plural names (#2850): See PR #3009. Thank you to @sgade for raising the issue.
  • Equality operator shows incorrect values based on value of __fulfilled (#2944): See PR #2990. Thank you to @scottasoutherland for raising the issue.

New

1.1.3

01 May 18:56
Compare
Choose a tag to compare

Fixed

  • @dynamicMember conflicting field name (#2950): The subscript setters have been changed to allow a selection set property named hash. #2965 Thank you to @renanbdias for raising the issue.
  • Disallow certain targetNames in code generation (#2958): apollo is no longer allowed as a target name otherwise it causes a conflict when importing Apollo as a module. #2972 Thank you to @moopoints for raising the issue.
  • Fully Qualify name of RootEntityType and mergedSources (#2949): Selection set types use fully qualified namespacing to prevent conflicts with other types. #2956 Thank you to @martin-muller for raising the issue.
  • SelectionSet Codegen __typename fix (#2955): Custom root types defined in the schema are now correctly applied to selection set fields typename definitions #2983 Thank you to @ynnadrules for raising the issue.

1.1.2

12 Apr 22:42
bdeff49
Compare
Choose a tag to compare

Fixed

  • Crash after calling cancel() on Cancellable (#2932): Calling cancel() on a non-subscription Cancellable will now correctly handle the lifetime of the internally Unmanaged object. #2943 - Thank you to @yonaskolb for raising the issue.
  • Deprecation messages are not escaped (#2879): If escaped characters are used in GraphQL deprecation messages they are now properly escaped in the rendered Swift warning or attribution message. #2951 Thank you to @djavan-bertrand for raising the issue.

Added

  • Add injecting additionalErrorHandler for upload operations to RequestChainNetworkTransport (#2948): Upload operations can now have custom error interceptors like other operations. #2948 Thank you to @RobertDresler for the contribution.

1.1.1

06 Apr 23:42
6de797f
Compare
Choose a tag to compare

Fixed

  • Version 1.1.0 does not compile when installed via CocoaPods (#2936): Module names not present in CocoaPods builds have been removed from type declarations. #2937 - Thank you to @simonliotier for raising the issue.
  • Crash when using mocks for Double Nested Arrays (#2809): Test mock data is now correctly applied to the selection set. #2939 - Thank you to @scottasoutherland for raising the issue.
  • In 1.1.0, passing custom scalars or GraphQLEnum to mocks fails (#2928): Test mock data is now correctly applied to the selection set. #2939 - Thank you to @scottasoutherland for raising the issue.