Possible reference mistake in subscription execution

[Yogu]

I'm a bit confused about MapSourceToResponseEvent in the execution specification for subscriptions. It explains how to map a sourceStream to a responseStream. Instead of specifying the behavior in case sourceStream completes, it talks about what happens when responseStream completes, even though there is no way how responseStream could complete on its own.

Am I right that the specification part just confused sourceStream and responseStream here?

Also, why is the operation called MapSourceToResponseEvent when it maps event streams? Shouldn't it be called MapSourceStreamToResponseEventStream?

[netlify]

✅ Deploy Preview for graphql-spec-draft ready!

Name	Link
🔨 Latest commit	012a913
🔍 Latest deploy log	https://app.netlify.com/sites/graphql-spec-draft/deploys/634d866f2cb33a0008714e39
😎 Deploy Preview	https://deploy-preview-994--graphql-spec-draft.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[benjie]

There's no EasyCLA on this PR, so I'm going to close and open it again. I agree with this change.

[benjie]

Hi @Yogu thanks for this fix. Just to summarise the discussion last night: this is indeed the right fix, and the other route of closing the streams (when the user unsubscribes, also (optionally) close the source stream) is covered in the prose above the Unsubscribe algorithm.