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

Fix consumption of event payload #4909

Merged
merged 1 commit into from
Feb 9, 2024
Merged

Fix consumption of event payload #4909

merged 1 commit into from
Feb 9, 2024

Conversation

sfmskywalker
Copy link
Member

@sfmskywalker sfmskywalker commented Feb 8, 2024

The 'input' parameter in 'PublishAsync', 'DispatchAsync' and related methods across multiple classes has been replaced with 'payload'. The renaming of 'input' to 'payload' provides a more intuitive understanding of the parameter as the actual content or data of the event being published or dispatched. It also includes changes in 'PublishInternalAsync' where the workflow input dictionary is now being populated with the payload.

BREAKING CHANGE

This is a breaking change due to the renaming of the Input property to Payload on the PublishEvent activity.
Although we could (still) consider to deprecate the Input property in favor of the new Payload property, I think we don't need to given the fact that passing around input from PublishEvent to Event has never worked before this PR, so I doubt that anyone is using it successfully anyway.

Fixes #4892

The 'input' parameter in 'PublishAsync', 'DispatchAsync' and related methods across multiple classes has been replaced with 'payload'. The renaming of 'input' to 'payload' provides a more intuitive understanding of the parameter as the actual content or data of the event being published or dispatched. It also includes changes in 'PublishInternalAsync' where the workflow input dictionary is now being populated with the payload.
@sfmskywalker sfmskywalker added the breaking Implementation requires an API-breaking change/major version increment label Feb 8, 2024
@sfmskywalker sfmskywalker merged commit d4e1cf0 into main Feb 9, 2024
2 checks passed
@sfmskywalker sfmskywalker deleted the issue(4892) branch February 9, 2024 07:20
@sfmskywalker sfmskywalker added the elsa 3 This issue is specific to Elsa 3 label Feb 9, 2024
@sfmskywalker sfmskywalker added this to the Elsa 3.1 milestone Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Implementation requires an API-breaking change/major version increment elsa 3 This issue is specific to Elsa 3
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Payload Loss in Publish-Event and Event Activities in Event.cs
3 participants