You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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:
id
s and we just took that as the input for codegen?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 itThe text was updated successfully, but these errors were encountered: