https://github.com/apollographql/apollo-kotlin-normalized-cache
Apollo Kotlin Normalized Cache
https://github.com/apollographql/apollo-kotlin-normalized-cache
android apollographql graphql graphql-client kotlin kotlin-multiplatform multiplatform
Last synced: 19 days ago
JSON representation
Apollo Kotlin Normalized Cache
- Host: GitHub
- URL: https://github.com/apollographql/apollo-kotlin-normalized-cache
- Owner: apollographql
- License: mit
- Created: 2024-06-18T17:46:23.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2025-04-10T13:14:25.000Z (20 days ago)
- Last Synced: 2025-04-11T01:54:57.024Z (19 days ago)
- Topics: android, apollographql, graphql, graphql-client, kotlin, kotlin-multiplatform, multiplatform
- Language: Kotlin
- Homepage: https://apollographql.github.io/apollo-kotlin-normalized-cache/
- Size: 3.74 MB
- Stars: 11
- Watchers: 7
- Forks: 3
- Open Issues: 21
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
[](http://community.apollographql.com/new-topic?category=Help&tags=mobile,client)
[](https://app.slack.com/client/T09229ZC6/C01A6KM1SBZ)[](https://central.sonatype.com/namespace/com.apollographql.cache)
[](https://s01.oss.sonatype.org/content/repositories/snapshots/com/apollographql/cache/)## 🚀 Apollo Kotlin Normalized Cache
This repository hosts [Apollo Kotlin](https://github.com/apollographql/apollo-kotlin)'s new normalized cache, aiming to replace the main repository version.
## 📚 Documentation
See the project website for documentation:
[https://apollographql.github.io/apollo-kotlin-normalized-cache/](https://apollographql.github.io/apollo-kotlin-normalized-cache/)The Kdoc API reference can be found at:
[https://apollographql.github.io/apollo-kotlin-normalized-cache/kdoc](https://apollographql.github.io/apollo-kotlin-normalized-cache/kdoc)## ⚠️ Disclaimer
This version is not yet stable and is subject to change. It is recommended to experiment with it in
non-critical projects/modules, or behind a feature flag.In particular,
- there are no guarantees about the format of the cached data, so you should assume that it may be lost when upgrading
- performance and size may not be optimal