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

clarify how to reference operationId and workflowId in case of clashes #125

Merged
merged 2 commits into from
Feb 1, 2024

Conversation

frankkilcommins
Copy link
Collaborator

fixes #124

Copy link
Member

@handrews handrews left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good - I might suggest creating a section up front that explains how various references and other connections are resolved. That would pull together the information that is duplicated in several spots here with other things we spoke about the other day such as referencing into full documents.

@frankkilcommins
Copy link
Collaborator Author

This looks good - I might suggest creating a section up front that explains how various references and other connections are resolved. That would pull together the information that is duplicated in several spots here with other things we spoke about the other day such as referencing into full documents.

I'll review deduplicating some of the verbiage as part of a separate issue

@frankkilcommins frankkilcommins merged commit 658bf05 into main Feb 1, 2024
2 checks passed
@frankkilcommins frankkilcommins deleted the frankkilcommins/issue124 branch July 31, 2024 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
implementor-draft In scope for first version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify how step operationId and/or workflowId should be prefixed if multiple sourceDescriptions are defined
3 participants