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

Message Attribute is not getting serialised in the message object. #943

Closed
Pronoy999 opened this issue Oct 28, 2021 · 6 comments
Closed
Milestone

Comments

@Pronoy999
Copy link

Describe the bug
The Message Object contains a member called Message Attribute, which should contain the SQS Message attributes.

Expected behaviour
The Message Object from the JustSaying Models should contain a Message Attribute.

Actual behaviour
The Message Object from the JustSaying Models does not contain Message Attribute.

System information:

  • OS: MacOS 11
  • Library Version 6.0.5
  • .NET version 5.0
@gkinsman
Copy link
Contributor

Hey @Pronoy999, thanks for reporting the issue.

In version 6, there's no way to make use of SQS message or system attributes. The MessageAttributes collection available on the base Message type is separate from SQS, and is still available, but can't be used on things like subscription filters as they're not mapped to the SNS message.

With version 7, we've added a new interface that you can pull into handlers called IMessageContextAccessor that provides access to publish and consume attributes. I can see that we haven't yet documented this behaviour so I created an issue for that here.

Unfortunately we're not really working on v6 anymore outside of security/maintenance issues, and the v7 release is still pending.

Thanks again for raising the issue.

@gkinsman
Copy link
Contributor

I should note also that there's a beta release available on nuget if you're willing to give that a try. Thanks!

@Pronoy999
Copy link
Author

Pronoy999 commented Oct 28, 2021

We can't use the beta on our app which would be running in production.
Is there a release date for v7?

@gkinsman
Copy link
Contributor

gkinsman commented Oct 28, 2021

Thanks again for your interest in the project @Pronoy999. We're currently in the process of updating some internal tooling to the latest beta, at which point we'll be able to start testing on some less important features.

I hope you understand that we have a very high quality bar for this project, as a lot of our business critical components rely on it. We need to be sure that it passes our internal verification before making a 7.0 release.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@martincostello
Copy link
Member

Tracking documentation for this feature in #944.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants