Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom cache id generation at compile time #2881

Closed
bignimbus opened this issue Mar 17, 2023 · 1 comment
Closed

Custom cache id generation at compile time #2881

bignimbus opened this issue Mar 17, 2023 · 1 comment
Labels
feature New addition or enhancement to existing solutions

Comments

@bignimbus
Copy link
Contributor

bignimbus commented Mar 17, 2023

Summary

I'm conveying some requests from side channels into an issue to gather feedback and initial thoughts on this functionality. In short, developers want the ability to get an operation identifier from an external source at compile time and use it as an id in the normalized cache.

Notes

Copying some notes from some offline discussion:

  • This section of the Kotlin docs describes the Kotlin API surface area that enables this functionality, so doing something similar would likely meet users' needs
  • Would it be easier if they provided the list of queries with their ids and we just took that as the input for codegen?
  • We currently output an operation-ids.json file to use to persist queries. But we could take that file as an input just as easily. If there is some build tool that is outputting that information in a standard format from a build tool we could use it
@bignimbus bignimbus added the feature New addition or enhancement to existing solutions label Mar 17, 2023
Copy link
Contributor

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New addition or enhancement to existing solutions
Projects
None yet
Development

No branches or pull requests

2 participants