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

Update Swift operationIdentifier to be a String? rather than the … #167

Merged

Conversation

kompfner
Copy link
Contributor

…inferred String. This brings it in alignment with the variables property, whose default value is provided by its protocol as nil.

See discussion in apollographql/apollo-ios#105 for context.

…inferred `String`. This brings it in alignment with the `variables` property, whose default value is provided by its protocol as `nil`.
kompfner pushed a commit to kompfner/apollo-ios that referenced this pull request Jul 10, 2017
@martijnwalraven martijnwalraven merged commit 9cf6fcf into apollographql:master Jul 12, 2017
@kompfner kompfner deleted the pk-optional-operation-ids branch July 12, 2017 07:49
kompfner added a commit to apollographql/apollo-ios that referenced this pull request Jul 13, 2017
* Update dependency on apollo-codegen to 0.14, so we can make use of operationIds

* Add support for sending operation ids rather than operation text when making requests

* Handle `operationIdentifier`s being of type `String?` rather than `String` (see apollographql/apollo-tooling#167)

* Update dependency on apollo-codegen to 0.15, so we can *actually* make use of `operationIdentifier`s (turns out they weren't ccorrectly made available in 0.14, as explained in apollographql/apollo-tooling#165)
ecstasy2 added a commit to ecstasy2/apollo-codegen that referenced this pull request Dec 22, 2017
…inferred `String`. This brings it in alignment with the `variables` property, whose default value is provided by its protocol as `nil`. (apollographql#167)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants