Last updated: Jan 2023
For up to date release notes, refer to the project's Changelog.
Please note: This is an approximation of larger effort work planned for the next 6 - 12 months. It does not cover all new functionality that will be added, and nothing here is set in stone. Also note that each of these releases, and several patch releases in-between, will include bug fixes (based on issue triaging) and community submitted PR's.
- Please report feature requests or bugs as a new issue.
- If you already see an issue that interests you please add a 👍 or a comment so we can measure community interest.
Please see our patch releases milestone for more information about the fixes and enhancements we plan to ship in the near future.
The @defer directive enables your queries to receive data for specific fields asynchronously. This is helpful whenever some fields in a query take much longer to resolve than others. Apollo Kotlin and Apollo Client (web) currently support this syntax, so if you're interested in learning more check out their documentation. Apollo iOS will release support for this directive in a 1.x minor version. More details TBD.
See Github 1.1 Milestone for more details.
- The ability to initialize fragment (and maybe selection set) models in a type-safe way
- Initialize mutable selection sets to add to the cache via local cache mutations (Currently you can only mutate fields on existing entities)
- Create API for clearing individual fields on entities from the cache in local cache mutations.
See Github 1.2 Milestone for more details.
- Right now we are naively generating schema types that we don't always need. A smarter algorithm can reduce generated code for certain large schemas that are currently having every type in their schema generated
- Create configuration for manually indicating schema types you would like to have schema types and TestMocks generated for
- Add configuration for disabling merging of fragment fields
- Recognize when multiple selection set types will end up being identical and use a shared model object with typealiases to reduce generated code
- Fix retain cycles and memory issues causing code generation to take very long on certain large, complex schemas with deeply nested fragment composition
- Optimize code generation performance by parallelizing computation and rendering of files
These are the major initiatives planned for 2.0/2.x:
- Networking Stack Improvements: The goal is to simplify and stabilise the networking stack.
- The updated network stack solved a number of long standing issues with the old barebones NetworkTransport but still has limitations and is complicated to use. Adopting patterns that have proven useful for the web client, such as Apollo Link, will provide more flexibility and give developers full control over the steps that are invoked to satisfy requests.
- We would love to bring some of the new Swift concurrency features, such as async/await, to Apollo iOS but that depends on the Swift team's work for backwards deployment of the concurrency library. It may involve Apollo iOS dropping support for macOS 10.14 and iOS 12.
See Github 2.0 Milestone for more details.
These are the major initiatives planned for 3.0/3.x:
- Cache Improvements: Here we are looking at bringing across some features inspired by Apollo Client 3 and Apollo Kotlin
- Better pagination support. Better support for caching and updating paginated lists of objects.
- Reducing over-normalization. Only separating out results into individual records when something that can identify them is present
- Real cache eviction & dangling reference collection. There's presently a way to manually remove objects for a given key or pattern, but Apollo Client 3 has given us a roadmap for how to handle some of this stuff much more thoroughly and safely.
- Cache metadata. Ability to add per-field metadata if needed, to allow for TTL and time-based invalidation, etc.
This major release is still in pre-planning, more details will come in the future.