Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Replace WorkflowHost with the launchWorkflowIn function. #447
Replace WorkflowHost with the launchWorkflowIn function. #447
Changes from all commits
8786269
bf58c4d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Insert after first sentence: Called on a newly created child [Job] of the given [scope], which defines the lifetime of the launched workflow tree. Cancelling that job ends the new workflow session.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reworded a bit, WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still find "It also gets a sub-scope" confusing since the scope is
this
, not a parameter. That's what got me talking about receiver elsewhere, although I take your point that that's a weird term too -- this ain't Smalltalk. Called on doesn't work for you?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be curious what the general opinion is on this. I still think of receivers as pretty much regular parameters, with slightly different syntax rules, but I have no reason to think that's a widely-shared mental model. "Called on" doesn't seem great to me though, since the receiver doesn't know anything about the method call – it makes sense from the caller's perspective, but not from the implementer's.