elsa-workflows / elsa-workflows/elsa-core

[BUG] Different type received in the input when using mass transit

Open
#5,237 1 comment 0 reactions 0 assignees View on GitHub
bug elsa 3 triaged
Dominant language
C#
Stars
7.9k
Forks
1.5k
Avg merge
15h 22m
Merged PRs (30d)
114

Description

## Description
We created a INotificationHandler and we tried getting the value of an input. That value was of type dictionary when using mass-transit and of type expando object when not using mass-transit.

## Steps to Reproduce
- Define a new
- Try to access the input
```csharp
public async Task HandleAsync(WorkflowExecuted notification, CancellationToken cancellationToken)
{
var workflowInput = notification.WorkflowExecutionContext.Input;
workflowInput.TryGetValue("Headers", out var headersInput)

```

3. **Attachments**:
No attachments

4. **Reproduction Rate**: Indicate how often the bug occurs when following these steps (e.g., "every time", "intermittently: about 50% of the time").
Every time.

5. **Video/Screenshots**: Sometimes, complex behaviors are better shown than described. If you think a video or screenshots would help clarify the issue, please include them.
No screenshots or video.

6. **Additional Configuration**:
Mass transit enabled/disabled.

## Expected Behavior
Received the same type no matter which provider you use.

## Actual Behavior
Different type received when inspecting the headersInput depending if mass-transit in enabled or not.

## Screenshots
No screenshot.

## Environment
Elsa version 3.1.0-preview.1209

## Log Output
No log.

## Troubleshooting Attempts
No attempt.

## Additional Context
No additional data.

## Related Issues
No related issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.